Related
Anyone know where I can get the latest stock ROM for a RAZR HD XT926 from a trusted source? I'm a bit nervous about downloading just any old file that claims to be a stock ROM. Who knows what could be embedded in it.
The latest OTA update from Verizon contains a bug fix that I desperately need, but my phone refuses to apply the update. I've given up working with Verizon and Motorola on this. Motorola level 2 support says they won't help because the phone is rooted, even though it wasn't at the time I spoke to them on the phone.
I've decided to go the route of flashing the ROM myself. I'm now rooted, bootloader is unlocked, safestrap is installed, and I've backed up the my working system with it. I've also installed rootkeeper so I can temporarily unroot before flashing.
Also after doing this will I need to reinstall and reconfigure all my apps? If so is there an easy way to back that all up so all I need to do is restore the backup?
Here you go!
chuckh1958 said:
Anyone know where I can get the latest stock ROM for a RAZR HD XT926 from a trusted source? I'm a bit nervous about downloading just any old file that claims to be a stock ROM. Who knows what could be embedded in it.
The latest OTA update from Verizon contains a bug fix that I desperately need, but my phone refuses to apply the update. I've given up working with Verizon and Motorola on this. Motorola level 2 support says they won't help because the phone is rooted, even though it wasn't at the time I spoke to them on the phone.
I've decided to go the route of flashing the ROM myself. I'm now rooted, bootloader is unlocked, safestrap is installed, and I've backed up the my working system with it. I've also installed rootkeeper so I can temporarily unroot before flashing.
Also after doing this will I need to reinstall and reconfigure all my apps? If so is there an easy way to back that all up so all I need to do is restore the backup?
Click to expand...
Click to collapse
Go to sbf dot droid-developers dot org That's where you'll find them!
Thanks. Are you pretty confident that they are clean?
Clean
chuckh1958 said:
Thanks. Are you pretty confident that they are clean?
Click to expand...
Click to collapse
Yes. I'm very confident they are. I've always used these to restore mine to stock when needed.
Awesome! Thanks. Now I just need to figure out how to flash the one I want. This is my first time. I'm guessing I just put the zip file on my sdcard and tell SafeStrap to recover using it.
Will I need to reinstall all my apps? Is there a way to prevent that? Mostly I'm concerned about apps that I've spent a lot of time setting up custom configurations for.
Back to Stock
chuckh1958 said:
Awesome! Thanks. Now I just need to figure out how to flash the one I want. This is my first time. I'm guessing I just put the zip file on my sdcard and tell SafeStrap to recover using it.
Will I need to reinstall all my apps? Is there a way to prevent that? Mostly I'm concerned about apps that I've spent a lot of time setting up custom configurations for.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2176753
That post will walk you through how to flash back to stock.
So I can't use safestrap to flash the stock ROMs downloaded from sbf dor droid-developers dot org?
Safestrap
chuckh1958 said:
So I can't use safestrap to flash the stock ROMs downloaded from sbf dor droid-developers dot org?
Click to expand...
Click to collapse
No you cannot.
I've got RSD Lite installed now and it successfully detects the device is fastboot mode. Next step is to unzip the XML file I downloaded and plug it into RSD Lite. Right?
How much risk do you think there is that I end up bricking the phone? Keep in mind that OTA updates always fail because the hash on the build.prop file doesnt match what its expecting even though I've never changed the build.prop file.
Will I be able to use SafeStrap recovery if the phone gets bricked?
Like I said this is the first time I've tried this and I'm trying to cover all the bases before I do anything dangerous.
chuckh1958 said:
I've got RSD Lite installed now and it successfully detects the device is fastboot mode. Next step is to unzip the XML file I downloaded and plug it into RSD Lite. Right?
How much risk do you think there is that I end up bricking the phone? Keep in mind that OTA updates always fail because the hash on the build.prop file doesnt match what its expecting even though I've never changed the build.prop file.
Will I be able to use SafeStrap recovery if the phone gets bricked?
Like I said this is the first time I've tried this and I'm trying to cover all the bases before I do anything dangerous.
Click to expand...
Click to collapse
You don't unzip the .xml, you just flash it in RSD. When you use RSD, you will no longer have SafeStrap installed. SafeStrap is only an app, not a true recovery replacement, it works in conjunction with the stock recovery. You can't use a true recovery replacement since your bootloader is locked.
If you're not comfortable with RSD, try the House of Moto here:
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/
RSD Lite failed to flash the phone. Error message was "failed flashing process - unknown fastboot command, (getvar).I do have the latest Android SDK installed (32 bit version) and it's in the my PATH. I can run fastboot from the command line and it does show a getvar command.
Prior to running RSD Lite I did temporarily unroot the phone with rootkeeper. Could that be the problem?
Ok I got to flash by ...
manually extracting the zip file
editing the xml file, and removing 2 lines that contained the text "getvar"
pointed RSDlite to the XML file instead of the zip file
From what I can see everything looks good on the phone. Now I just have to let it finish reinstalling all the apps.
I just wanted to post the steps here in case anyone else stumbles onto this thread and has the same problem.
I did lose root. Any way to get it back?
chuckh1958 said:
I did lose root. Any way to get it back?
Click to expand...
Click to collapse
We have root on the newest build now! In the general forum.
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
scott_doyland said:
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
Click to expand...
Click to collapse
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
kieranc88 said:
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
Click to expand...
Click to collapse
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
scott_doyland said:
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
Click to expand...
Click to collapse
Yeah,send it,I'll try copying it,unrooting and then trying the update
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
And will it matter what version of the stick recovery I'm using( if there are different versions)
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
tee_pot said:
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
Click to expand...
Click to collapse
OK,well at the moment I'm trying out cm11 unofficial builds,I'll see how they go, I'll try the full unroot option when I restore my cwm backup and reflash stock recovery and see if that works ,as I only tried the temporary unroot option in supersu(which is probably leaving some root files behind so it can reinstall su ) if that don't work I'll flash back to stock and try again.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I will send file tomorrow when I'm at my PC.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I have attached the file /system/etc/install-recovery.sh file to this post (had to gzip it as couldnt upload when it was just called .sh)
Im not sure what the original persmissions of the file should be on your phone, but if you make it read/write/executable by everyone then should be OK I guess.
As I mentioned it'd be good if you unrooted and did a backup and extracted the file to see the contents (before copying over the file). That would first tell you for sure if the file does revert back to original or if it stays as a 'superSU' file when you unroot.
If its reverted back to original then my theory is wrong anyway so no need to copy over the file.
Re the stock recovery type/version being different from what is expected - I dont know if that makes a difference to the OTA working or not. Its an interesting question though so I may do some googling and find out.
I also have a UK retail stock recovery.img (taken with CWM) (my phone is 16GB from phones4u). So if you want that you can have it. Should rule out the recovery type as a problem.
FYI the install-recovery.sh original file actually flashes a new stock recovery when an OTA is performed. At least if you look in the comments of the file I attached above thats what it says.
Hi guys, as I cant stand the ads I'm thinking of rooting the device but I wonder if I can have OTA updates after this and if yes, do I have to re-root the phone after the updates?
thxxx
epivitor said:
Hi guys, as I cant stand the ads I'm thinking of rooting the device but I wonder if I can have OTA updates after this and if yes, do I have to re-root the phone after the updates?
thxxx
Click to expand...
Click to collapse
If you have non gpe device then yes root will deny ota.
No my device isnt the gpe.
How can I update my phone then ?
epivitor said:
No my device isnt the gpe.
How can I update my phone then ?
Click to expand...
Click to collapse
flash stock rom
update via OTA
again root..
solved...
reversegear said:
flash stock rom
update via OTA
again root..
solved...
Click to expand...
Click to collapse
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
epivitor said:
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
Click to expand...
Click to collapse
afaik OTAs cannot be installed via PC
name itself says Over The Air
reversegear said:
afaik OTAs cannot be installed via PC
name itself says Over The Air
Click to expand...
Click to collapse
I wanted to say if I get the OTA update from another source not over the air of course, could I flash it without porblem through usb cable?
epivitor said:
I wanted to say if I get the OTA update from another source not over the air of course, could I flash it without porblem through usb cable?
Click to expand...
Click to collapse
no you cannot flash OTAs via PC
S0bes said:
If you have non gpe device then yes root will deny ota.
Click to expand...
Click to collapse
Really? My XT1032 is rooted since i bought it and I was still able to apply the February OTA. Didn't wait for it to reach my phone though - I've downloaded it here on XDA, then checked for updates.
epivitor said:
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
Click to expand...
Click to collapse
you can install CWM.
Then make a full backup. You can move it on your pc or let it take space on your phone.
After that you can apply any patches via CWM or install root or whatsoever
When your phone will show the next update you should:
1) Boot into CWM and recover your backup. BUT! You should recover only part of it. The system part.
backup and restore -> advanced restore from /sdcard -> choose your backup -> restore system
2) wait till it complete.
Now you can delete your backup.
Reboot your phone (reboot system now)
After that you will see 2 messages and if you wanna be able to apply ota you have to make the right choises
Q: ROM may flash stock recovery on boot. Fix?
A: NO
Q: Root access is missing. Root device?
A:NO
After all that steps you'll get:
1) clear system part (which means no root, modified files etc)
2) default recovery
I've read "mixed" opinions about this; some say rooted devices lose updates and some say otherwise. I've also heard that if you flash ROM A on top of ROM B that's your original ROM, and you get signature errors you no more receive OTA updates. By the way, I was able to receive OTA updates on my Asia Retail XT1033 that was flashed to Retail UK XT1032. It would be cool if some senior member here shed some light on this subject.
knizmi said:
Really? My XT1032 is rooted since i bought it and I was still able to apply the February OTA. Didn't wait for it to reach my phone though - I've downloaded it here on XDA, then checked for updates.
Click to expand...
Click to collapse
yes, it can be so. I heard about the same situation from few people. But other still can not apply ota with root
S0bes said:
yes, it can be so. I heard about the same situation from few people. But other still can not apply ota with root
Click to expand...
Click to collapse
I think that people who have reported that they can't apply the OTA update had messed their /system partition in other ways than just rooting.
I've studied the update package and all it does is that it first checks if the files (and only those files) that are going to be updated are untampered with and if everything is allright, they are patched.
To sum it up - you can have extra files on your /system folder (like the su binary), but all of the updated files must be stock. The updater really doesn't care if su, xposed or other mods are present.
knizmi said:
I think that people who have reported that they can't apply the OTA update had messed their /system partition in other ways than just rooting.
I've studied the update package and all it does is that it first checks if the files (and only those files) that are going to be updated are untampered with and if everything is allright, they are patched.
To sum it up - you can have extra files on your /system folder (like the su binary), but all of the updated files must be stock. The updater really doesn't care if su, xposed or other mods are present.
Click to expand...
Click to collapse
Is there a problem if some of the apps are disabled ? (not with titanium backup but through settings->apps->select the app ->disable)
epivitor said:
Is there a problem if some of the apps are disabled ? (not with titanium backup but through settings->apps->select the app ->disable)
Click to expand...
Click to collapse
No, disabled apps are still where they are supposed to be. The OTA updater checks if the file is there (it is), if the fingerprint matches (it does) and then it patches the app even when it's disabled.
I managed to pull the 5.0 Lollipop OTA update file and load it to Android File Host.
Word of warning, should you try to use this file to update, you will likely lose root, possibly without the chance to root once complete or even ODIN back to 4.x. This is primarily for devs to use to try to make pre-rooted and custom ROMs with.
The link to the file is below:
https://www.androidfilehost.com/?fid=95916177934552137
@muniz_ri, @RockRatt, @iB4STiD and @Joe-Tech, I believe you guys may be interested in this.
May the odds ever be in our favor.
@Apoplectic1 you awesome man, will see what i can do with it
Doesn't flash, wipes /Data stating "Footer is wrong"
Apoplectic1 said:
I managed to pull the 5.0 Lollipop OTA update file and load it to Android File Host.
Word of warning, should you try to use this file to update, you will likely lose root, possibly without the chance to root once complete or even ODIN back to 4.x. This is primarily for devs to use to try to make pre-rooted and custom ROMs with.
The link to the file is below:
https://www.androidfilehost.com/?fid=95916177934552137
@muniz_ri, @RockRatt, @iB4STiD and @Joe-Tech, I believe you guys may be interested in this.
May the odds ever be in our favor.
Click to expand...
Click to collapse
Thanks for the heads up. I will create the ROM later tonight.
DankHeals said:
Doesn't flash, wipes /Data stating "Footer is wrong"
Click to expand...
Click to collapse
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
muniz_ri said:
Thanks for the heads up. I will create the ROM later tonight.
Click to expand...
Click to collapse
I've probably told you this about a dozen times now, but you are the man! :highfive:
Apoplectic1 said:
I've probably told you this about a dozen times now, but you are the man! :highfive:
Click to expand...
Click to collapse
No worries and thanks for capturing the ota.
Apoplectic1 said:
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
Click to expand...
Click to collapse
I fully unrooted and went stock before attempting, but that's a shame. Thought it would be flashable via update in stock recovery. :/
cant wait to have this flashable.. been waiting soooo long
When O when will the wait end.... Canada S4 and I still can't install this AT&T one
How to use this file ???
DankHeals said:
Doesn't flash, wipes /Data stating "Footer is wrong"
Click to expand...
Click to collapse
Because you flashed the archived cfg file. To flash the update you have to unpack the zip file and change the extension of the CFG file to ZIP. But anyway even this cfg fails to install, so don't try because i already did.
Update via adb or external sd card using stock recovery doesn't work !
Is there a way to flash it ???
lordnihilusmd said:
Because you flashed the archived cfg file. To flash the update you have to unpack the zip file and change the extension of the CFG file to ZIP. But anyway even this cfg fails to install, so don't try because i already did.
Update via adb or external sd card using stock recovery doesn't work !
Is there a way to flash it ???
Click to expand...
Click to collapse
Thanks for the info... been looking for a way to flash this without success
W1zz_ said:
Thanks for the info... been looking for a way to flash this without success
Click to expand...
Click to collapse
You could try pushing the cfg file to /cache/fota, uninstall Safestrap, full unroot, reboot and then installing the update the standard way, but getting root afterward is iffy.
Can somebody pull out the modem?
Apoplectic1 said:
You could try pushing the cfg file to /cache/fota, uninstall Safestrap, full unroot, reboot and then installing the update the standard way, but getting root afterward is iffy.
Click to expand...
Click to collapse
Thanks man, my situation is a little more complicated however since I have the i337m(Canadian S4) wasn't sure I'd be able to install this OTA in any way. Kind of came to the conclusion that I will have to wait for a custom Rom, unless my understanding of how this all works is wrong.
I will try but i already did full unroot . When flashing via recovery it says something like frameworkres-apk has unexpected content ... Standard way ? but it will tell me software update interrupted
Apoplectic1 said:
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
Click to expand...
Click to collapse
It won't flash even without root. Tried flashing via stock recovery, no dice just like the others. Flashing results in wiping /data.
Short road...
Easiest way possible odin back to NB1 then take the OTA to lollipop that's the easiest way man
lordnihilusmd said:
I will try but i already did full unroot . When flashing via recovery it says something like frameworkres-apk has unexpected content ... Standard way ? but it will tell me software update interrupted
Click to expand...
Click to collapse
brownie9987 said:
Easiest way possible odin back to NB1 then take the OTA to lollipop that's the easiest way man
Click to expand...
Click to collapse
OTA from ODIN stock has never worked for me. Maybe it's because it's SIM-less?
What do you mean by Simless?
Hi
I really need help to go stock on my device.
I unlocked my bootloader, flashed TWRP and Magisk on stock rom and installed the ViperU Magisk Module.
I also made a NANDROID of the stock ROM before, unfortunately there is no Recovery in it, since i had TWRP already installed.
Then an OTA (oktober 17 security patch) was available for my device and i startet the install process, but it didn't install.
TWRP open recovery would run not even 1 second then exit.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
And is there an other way available?
Thanks!
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000
Nightmare
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000[/QUOTE said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
michaelbsheldon said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Hi
Yes, unfortunately there's nothing available for my device.
Does the phone boot into os?
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
schmeggy929 said:
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
Click to expand...
Click to collapse
Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
2eli0 said:
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
Click to expand...
Click to collapse
since s-off is still temporary it will go back to s-on as soon as you boot into recovery or rom.
also, i flashed the 1.27.401.5 ruu, since i wanted to see if the update to 1.27.401.12 ota works with twrp and magisk installed.
it does, just remember to keep recovery read only!
What do you mean by "read only"? Is there a setting where I can do that?
2eli0 said:
What do you mean by "read only"? Is there a setting where I can do that?
Click to expand...
Click to collapse
If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Nightmare[ITA said:
;75529278]If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Click to expand...
Click to collapse
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
2eli0 said:
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
Click to expand...
Click to collapse
Pretty much, ya. I missed that part the first time too
Nightmare[ITA said:
;75529808]Pretty much, ya. I missed that part the first time too
Click to expand...
Click to collapse
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
2eli0 said:
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
Click to expand...
Click to collapse
Yes, over the last few months AFH has been extremely slow.
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
I have already seen that, but its like 400 mb big, if I remember correctly, hence not the entire files, right?
schmeggy929 said:
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
The htcdev stuff is source only. No good. Also, once you flash twrp you can't take ota. You must be stock to take ota (s-off and bootloader remain untouched and do not matter for flashing, there is no need to s-on nor relock the bootloader ever).
To achieve stock just flash the same firmware you currently use as a zip from the external sdcard. The only things lost is root and twrp.
Nightmare[ITA] said:
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
Click to expand...
Click to collapse
Yeah i guess you are right it is the source code. Even with TWRP stills seems like a lot of work to update. Ya'll need some custom ROMs installed. Flash signed firmware.zip, reflash TWRP and flash updated ROM. All done. If by chance you ever needed to return to stock, flash your system image backup. Ya'll make things so complicated when they really aren't. lol
Nightmare[ITA said:
]Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Click to expand...
Click to collapse
Well, I managed to do it exactly the way you did.
Everything worked just fine. I changed the CID to HTC__034 and flashed the ruu file updated to Oreo and flashed TWRP kept it at read only and rooted the phone.
Thanks for that :good: