current mine is 1.17.707.9 KK4.4.4 rooted and i changed permission to write external sd card myself, unlocked s-on, and can't find stock rom anyway.
and OTA update file come with 2.19.707.1 WWE Asia >> https://drive.google.com/file/d/0Bz42d4oUm2q_SWNaTV9zbTBHSkU/view?usp=sharing <<
and it can't update though 'cause i did change system files, anyway.
i just wonder that there will have a way to change or convert OTA file to TWRP?
so if it does, HOW?
i'm so hopeless at this point.
PLEASE
THANKS
Did you return to stock everything (rom, kernel, recovery) before trying to apply the OTA?
Also, as soon as you install the update, please please make a twrp backup of the stock and unrooted ROM and post it.
Related
Hi
I'm desperately looking for any Bell mobility stock 1.34.666.5 or Over.
The camera button is not working so I sent my phone to repair but they send it back because I do not have the right rom that was provided with my phone. I was able to unroot and put back 1.34.666.1 (the only one that is available it seems) but the technical support told me that my phone shipped with 1.34.666.5 and that they can't do anything unless I'm putting back this rom.
I tried getting OTA updates for 1.34.666.1 but it's not available. Minimum rom # to get OTA updates have to be 1.34.666.5
I'm screwed.
Regards
I have a nandroid backup of the stock ROM...it's rooted though.
Will I be able to flash using Clockwork Recovery? I can manage to remove root after flashing, I think.
Yes, flashable via Clockwork.
I'll let you know when I have it uploaded.
...and it's up.
https://xda:[email protected]/_xda/Bell.DZ.Stock.ROOTED.7z
Some notes:
- I only included the system and boot portions of the nandroid backup due to privacy concerns
- As such, you should do a system and boot restore (after a full wipe, of course) under "Advanced Restore"
- As mentioned earlier, this is rooted (so you'll need to unroot)
Hope this helps. Let us know how it goes.
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Tonkadan said:
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Click to expand...
Click to collapse
That's good to hear. I'd recommend making your own nandroid backup immediately.
As for the bootloader, you're sure you flashed the ENG HBOOT during the rooting process? If that's the case, I'm not sure where you can find the stock HBOOT...
Yes, I installed the Eng HBoot.
I'm trying now renaming the OTA update.zip, put on the root of sdcard and make recovery to install that update but I got an error about getprop CID?? and the update failed...
Still looking for a solution.
How did you make out Tonkadan? I'm in the same boat. I heard that if you did apply this update that you would not be able to root your phone anymore.
I' still rooted. I'm unable to go back to stock. I'm using cyanogenmod 7 for now but would really want to go back to stock if somone have the official Bell rom over 1.34.666.5.
... Or any way to get OTA updates for RUU 1.34.666.1 that is available on shippedroms.com
As this post: http://forum.xda-developers.com/showthread.php?t=1043541
I would like to go back Stock and get OTA updates. My problem is I can't use the unrooting tutorial on the G2/Z wiki as it require to flash a stock Rom and the only available stock ROM for my carrier is too old to get the OTA update (1.34.666.1 and OTA is looking for 1.34.666.5)
TheSPam gave me is nandroid backup so now I have the 1.34.666.5 Version but I'm still rooted. I'm trying to get back 100% stock.
When I'm trying to do the OTA update, after rebooting to flash the update clockworkmod recovery interfere and the OTA update Fail.
I've tried renaming the Update to update.zip, put this on the root of my sdcard and get clockworkmod to install the update from sdcard but I get an error like getprop CID and the update fail.
how can I get back to 100% Stock, unrooted and be able to get the OTA update?
Tonkadan said:
As this post: http://forum.xda-developers.com/showthread.php?t=1043541 I would like to go back Stock and get OTA updates. My problem is I can't use the unrooting tutorial on the G2/Z wiki as it require to flash a stock Rom and the only available stock ROM for my carrier is too old to get the OTA update (1.34.666.1 and OTA is looking for 1.34.666.5) TheSPam gave me is nandroid backup so now I have the 1.34.666.5 Version but I'm still rooted. I'm trying to get back 100% stock. When I'm trying to do the OTA update, after rebooting to flash the update lockworkmod recovery interfere and the OTA update Fail. I've tried renaming the Update to update.zip, put this on the root of my sdcard and get clockworkmod to install the update from sdcard but I get an error like getprop CID and the update fail. how can I get back to 100% Stock, unrooted and be able to get the OTA update?
Click to expand...
Click to collapse
What makes you think opening a new tread is going to solve your issue http://forum.xda-developers.com/showthread.php?t=1043541 quicker?
Absolutely nothing. I started a new thread because the issue in the original post is resolved and i'm facing a complete new problem. Because the initial issue was very specific to my carrier I tough starting a new thread for the new issue may get more answers cause its more generic.
It is that bad?
OK Short Update,
I've been able to install the OTA Update using Recovery. I got the update notification then downloaded the update. I opened the zip file and modified the updater-script to bypass CID check adding || 1 == 1 (So the CID check will always return true then I click ok on the System Update notification.
Phone rebooted and in recovery I selected install ZIP from sdcard. Pointed to the OTA update and everything went fine.
So I'm unrooted now but i'm still S-Off and because I installed the OTA update over a rooted nandroid backup, SuperUser is still in the rom and I can't delete it.
I'm still not able to return the phone for repair and still don't know what to do.
And the last problem, Wifi doesn't work anyore on my phone. It says wifi error and I can't get the mac Adress on Info about your phone, nor the bluetooth address.
Any solution?
Any news about that? I'm still stuck with stock rom but no wifi and bluetooth and can not delete superuser from apps drawer. Thanks
You cannot delete superuser as its embedded in your ROM. Superuser doesn't magically appear when you get root, its put on ROMs for your use or put on during the root process for certain devices.
Now anyways, onto your predicament. You should search your vendors website for an update RUU (eg. vodafone website) or in the android development section. Once you find one to your liking you just follow the Vision Wiki guide to unrooting. There really is no easier way to remove all the aspects of a root without following those steps. Ultimately following that guide will help you restore your Desire Z/G2 to a normal one with no superuser, superCID or secu-flag unlock.
Just a side note, it will be rather difficult for you to obtain a stock ROM from any other user because since they don't have root access or clockworkmod they can't make you a backup of their 1.72 based ROMs.
I recently unlocked the bootloader of an HTC One (M8) running Kitkat, installed TWRP then flashed a .ZIP file to root the phone. Now Lollipop has been released there's an OTA available on the phone but I'm not able to update through it. I've seen different posts all over the place about how you have to just install the stock recovery or how you have to use an RUU or how you have to use a NANDroid backup so the opinions are quite conflicting.
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Charlular said:
I recently unlocked the bootloader of an HTC One (M8) running Kitkat, installed TWRP then flashed a .ZIP file to root the phone. Now Lollipop has been released there's an OTA available on the phone but I'm not able to update through it. I've seen different posts all over the place about how you have to just install the stock recovery or how you have to use an RUU or how you have to use a NANDroid backup so the opinions are quite conflicting.
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Click to expand...
Click to collapse
No need to unroot. You just need a stock recovery.
Charlular said:
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Click to expand...
Click to collapse
Let me try to clarify the confusion based on my experience with the Lollipop OTA update. First, you need to remember that, during the OTA update, the software checks for two things: 1) the version of the recovery; and 2) whether any system files has been modified (described in my earlier post).
As a result, you only need stock recovery (from 4.4.4 or 5.0.1) to initiate the OTA update (as mentioned by the other poster). If no system files were altered as a result of your root access, your OTA should finish without errors.
However, root itself and what people do after they have root access often mean some system files were altered. Hence, they need to use either RUU or TWRP backup to restore they all files back to the factory version.
Finally, as for RUU vs. TWRP:
The RUU or TWRP version must match that to your carrier version of M8. The RUU is the better option, but not available for all carrier versions. When RUU is not available, people rely on TWRP nandroid backup generated by other users.
Bottom line or my advice:
First do a TWRP backup before you start anything. If anything goes wrong, you can always revert back to the working status as it is now.
To begin, go back to stock recovery, and see if the OTA update will go through. If not, you will see red triangle. Then hold Vol + and tap power button once to see the error messages. See my post above. If you ran into the same error as I did, you'll know what to do (RUU or TWRP backup to return to stock).
ikeny said:
Let me try to clarify the confusion based on my experience with the Lollipop OTA update. First, you need to remember that, during the OTA update, the software checks for two things: 1) the version of the recovery; and 2) whether any system files has been modified (described in my earlier post).
As a result, you only need stock recovery from (4.4.4 or 5.0.1) to initiate the OTA update (as mentioned by the other poster). If no system files were altered as a result of your root access, your OTA should finish without errors.
However, root itself and what people do after they have root access often mean some system files were altered. Hence, they need to use either RUU or TWRP backup to restore they all files back to the factory version.
Finally, as for RUU vs. TWRP:
The RUU or TWRP version must match that to your carrier version of M8. The RUU is the better option, but not available for all carrier versions. When RUU is not available, people rely on TWRP backup generated by other users.
Bottom line or my advice:
First do a TWRP backup before you start anything. If anything goes wrong, you can always revert back to a work status as it is now.
To begin, go back to stock recovery, and see if the OTA update will go through. If not, you will see red triangle. Then hold Vol + and tap power button once to see the error messages. See my post above. If you ran into the same error as I did, you'll know what to do (RUU or TWRP backup to return to stock).
Click to expand...
Click to collapse
A very well-worded answer
This is a public service announcement to save people headaches. RTFM. You cannot ever now, or in the past, take an OTA with a custom recovery. You must always have a stock recovery and system to do so. Period. If you do install a custom recovery, freeze the update center with Titanium, Rom Toolbox, or the like, so that you will remember you have a custom recovery and not accidentally take an update.
I hope this helps someone out there
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Grizzie said:
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Click to expand...
Click to collapse
.this is referring to stock software updates, unless it's updates of the rom, which you won't even receive if you're on a custom rom...to update a custom rom, you just download the updated version, or the OTA if the rom is so capable, and flash it in twrp like the first version you downloaded
Grizzie said:
So what is the simplest way to update to the OTA firmware with a phone that is rooted with twrp, and a custom ROM? Is there a way to disable twrp without having to un-root? That way it might be possible to update to the OTA firmware. Please correct me if I'm wrong.
Click to expand...
Click to collapse
Wait for a flashable zip for TWRP. You can revert to stock to take an OTA. Being rooted is not a problem per se, it's the custom recovery and having non stock roms. In theory you could flash the stock recovery and bootloader and then take an OTA. However, not having stock system/apps could likely create havoc
In case you do happen to try and install it, here's a fix for your bootloops: http://forum.xda-developers.com/showthread.php?p=60117595
I finally managed to find out where my phone downloaded the Sprint Nougat OTA file, and copied it to my SDcard.
My phone is a Sprint HTC 10. The bootloader is unlocked and my recovery is TWRP, but other than that I am stock and unrooted.
Everyone says you need to be on stock everything to install an OTA update (though I had no issues installing previous OTA updates directly, but all of those were small), so I was reading up on flashing stock recovery.... but several people commented that flashing a stock recovery on their phone wiped it. I really don't want to take that risk, and with TWRP I can make a backup of my entire phone. So I wanted to know, if flashing an OTA update fails from TWRP, could that brick my phone bad enough that I wouldn't be able to flash the TWRP backup to restore it? Or can I recover as long as I can boot into... well, recovery. Would the OTA update overwrite the recovery too? Especially if I try to install it from within that recovery?
I was told to extract the "update.zip" file from the OTA.... but there is none in there, is the OTA zip file itself what they meant by "update.zip"?
flashing an ota with twrp won't work...at least it won't update the firmware bits.