Tried to update to Lolipop build using the OTA.
Getting this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wrong recovery. Can't use EU recovery for India version.
Use this one : http://forum.xda-developers.com/showpost.php?p=58631821&postcount=4338
ckpv5 said:
Wrong recovery. Can't use EU recovery for India version.
Use this one : http://forum.xda-developers.com/showpost.php?p=58631821&postcount=4338
Click to expand...
Click to collapse
Am still getting the same error.
atuladhikari said:
Am still getting the same error.
Click to expand...
Click to collapse
How can it be SAME error ? Post a screenshot.
The earlier screenshot shows clearly that it needs htc_asia_india but your device has htc_europe
If the recovery is properly installed, when there are more errors, they should be different errors.
For example, an expected contents error.
It's not on about the recovery, its saying the ROM on the phone has the EU build.prop fingerprint as opposed to the one it needs
EddyOS said:
It's not on about the recovery, its saying the ROM on the phone has the EU build.prop fingerprint as opposed to the one it needs
Click to expand...
Click to collapse
I see.. the system is smarter now. You have htc_europe ROM installed on a htc_asia_india device, do the OTA checking, the system will download htc_asia_india instead of htc_europe
Not necessarily. If the OTA was downloaded from HTC via the phone then the ROM is probably correct and the OP may have just changed the build.prop for some reason. We won't know unless they say so.
EddyOS said:
Not necessarily. If the OTA was downloaded from HTC via the phone then the ROM is probably correct and the OP may have just changed the build.prop for some reason. We won't know unless they say so.
Click to expand...
Click to collapse
So what do i need to do?
Have downloaded the OTA 4 times already and having the same error.
ckpv5 said:
I see.. the system is smarter now. You have htc_europe ROM installed on a htc_asia_india device, do the OTA checking, the system will download htc_asia_india instead of htc_europe
Click to expand...
Click to collapse
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
atuladhikari said:
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
Click to expand...
Click to collapse
Restore my 3.35.720.1 stock nandroid from the backups thread, and then flash this recovery, and then download the ota
atuladhikari said:
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
Click to expand...
Click to collapse
I know it can't be ... that post is not for you.
I asked for another screenshot after you flashed the 3.35.720.1 that I gave you the link before. It should not be a htc_europe problem anymore but maybe other errors.
You did fastboot flash recovery 3.35.720.1_recovery.img after you downloaded the recovery image, right ?
atuladhikari said:
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
Click to expand...
Click to collapse
You're using the stock recovery from Lollipop, hence it saying LRX22C release-keys at the top. If this is the wrong recovery you'll get an error. It HAS to be the recovery that came with your build
EddyOS said:
You're using the stock recovery from Lollipop, hence it saying LRX22C release-keys at the top. If this is the wrong recovery you'll get an error. It HAS to be the recovery that came with your build
Click to expand...
Click to collapse
where can i can get recovery for my build?
so the way my noob brain has understood.
i need to first need to flash unsuperuser.zip
the flash 3.35.720.1_recovery.img and redownload the OTA?
or flash unsuperuser.zip
and then flash 4.16.401.10_firmware.zip?
BUMP
Help someone!!!
I still have no Lollipop love!!!
atuladhikari said:
Help someone!!!
I still have no Lollipop love!!!
Click to expand...
Click to collapse
Flash the RUU from the stock backups thread
Related
Today I receive this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, before do bad thing, I want to know if I can update my HOX via OTA, without re-unlock bootloader or anything else.
Right now,I'm using the stock rom, I only unlock bootloader, flash custom recovery in order to root it.
Thanks
You need to re flash stock recovery
Sent from my HTC One X using xda app-developers app
tomascus said:
You need to re flash stock recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I already do it and nothing. Does anyone know if I update the firmware to 1.36 (my CID is HTC__044) and flash stock boot.img will work? Anyone can provide me just the boot.img file?
And if I flash the stock RUU 2.17.707.3 (which is the one I got) I don't have to update the firmware manually?
All I want is to update to stock JB via OTA.
Thanks.
What is the question?
The fact you got the update means you are good to go. Probably if you boot in bootloader it says re-locked?
The update will update your hboot to 1.36 and firmware to stock 3.14
Where you will lose cwm and root.
If you want root then you need to re-unlock it by cmd and with unlock file you got from the first time.
Sent from my HTC One X
xSilv85 said:
What is the question?
Click to expand...
Click to collapse
The question is why I can't update?. As I say already flash stock recovery, and I have the bootloader unlocked.
But what happens when you try to update?
BenPope said:
But what happens when you try to update?
Click to expand...
Click to collapse
After download the update, the phone reboot and an exclamation red icon appears, then reboot again and you can see that nothing is updated.
Did you got the smaller update too or not? When i flashed stock recovery from RUU i got the small battery update first.
Do you have stock recovery from when you unlocked the phone?
Sent from my HTC One X
xSilv85 said:
Did you got the smaller update too or not? When i flashed stock recovery from RUU i got the small battery update first.
Click to expand...
Click to collapse
Yes.
xSilv85 said:
Do you have stock recovery from when you unlocked the phone?
Click to expand...
Click to collapse
Yes, also I flashed again but nothing. I think that the problem might be that I uninstall some bloatware apps. Anyone know which bloatware apps are updated with the OTA update?
Ah that's the problem, your rom has to be as it came out of the box ! Otherwise it won't work
I should back this rom up and copy it to pc, then run the matching ruu to get back to stock or get the matching nandroid backup in the general section - nandroid backup collection from matt95 !
It's he easiest way in my opinion
Device: HTC M8 sprint h/k
Followed this post and was able to unlock:
http://forum.xda-developers.com/showthread.php?t=2718150
But during update, it shows error message "unable to locate zip file":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could this be caused by Custom Recovery TWRP 2.7?
Battery is at 30%, but I don't think it has anything to do with this.
lesterhung said:
Device: HTC M8 sprint h/k
Followed this post and was able to unlock:
http://forum.xda-developers.com/showthread.php?t=2718150
But during update, it shows error message "unable to locate zip file":
Could this be caused by Custom Recovery TWRP 2.7?
Battery is at 30%, but I don't think it has anything to do with this.
Click to expand...
Click to collapse
Stock Rom? If so, it will only install with stock recovery.
TWRP recovery only installs custom Rom/s and custom Rom updates (if the custom Rom supports ota updates).
Sent from my HTC One_M8 using XDA Premium 4 mobile app
spikeydoo2006 said:
Stock Rom? If so, it will only install with stock recovery.
TWRP recovery only installs custom Rom/s and custom Rom updates (if the custom Rom supports ota updates).
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I use stock rom and run stock rom update.
How can I use stock recovery?
Is this method work?
Collection of Stock Recovery
thanks a lot
zxc61529 said:
I use stock rom and run stock rom update.
How can I use stock recovery?
Is this method work?
Collection of Stock Recovery
thanks a lot
Click to expand...
Click to collapse
You can find your recovery here http://forum.xda-developers.com/showthread.php?t=2701376
But if you have sprint device then search sprint thread.
Jyotirdeb said:
You can find your recovery here http://forum.xda-developers.com/showthread.php?t=2701376
But if you have sprint device then search sprint thread.
Click to expand...
Click to collapse
HI~
I find my stock there
http://forum.xda-developers.com/showthread.php?t=2729173
How can I get stock recovery?
or
I just follow the instruction running the RUU utility
Can it work ?
Can I get back stock recovery?
zxc61529 said:
HI~
I find my stock there
http://forum.xda-developers.com/showthread.php?t=2729173
How can I get stock recovery?
or
I just follow the instruction running the RUU utility
Can it work ?
Can I get back stock recovery?
Click to expand...
Click to collapse
Follow the link I have posted.On the first post there are stock roms.Scroll down a bit and It is written in BIG LETTERS Stock Recoveries.Download the recovery which you need.Then flash it via fastboot.For RUU to work you need to have a stock recovery.
If you are a sprint owner check this thread.http://forum.xda-developers.com/showthread.php?t=2736048 Read the OP very carefully before posting.
Hi All,
I'm on 1.25.720.1 Indian Version, unrooted & stock recovery from here : http://forum.xda-developers.com/devdb/project/dl/?id=5178
When I try to update OTA, stock recovery is giving error(image attached)
I have tried almost everything. But no solution. Same error is showing every time.
Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jithumon said:
Hi All,
I'm on 1.25.720.1 Indian Version, unrooted & stock recovery from here : http://forum.xda-developers.com/devdb/project/dl/?id=5178
When I try to update OTA, stock recovery is giving error(image attached)
I have tried almost everything. But no solution. Same error is showing every time.
Please help.
Click to expand...
Click to collapse
You should now change this topic header to [Solved] as you already find a fantastic way to deal with it. Good work dear.
vbrsekhar said:
You should now change this topic header to [Solved] as you already find a fantastic way to deal with it. Good work dear.
Click to expand...
Click to collapse
Thankyou bro.... I forgot about this...
vbrsekhar said:
You should now change this topic header to [Solved] as you already find a fantastic way to deal with it. Good work dear.
Click to expand...
Click to collapse
What was that fantastic way???
spatone said:
What was that fantastic way???
Click to expand...
Click to collapse
It was the stock recovery from king doing the problem.
I found the stock Indian recovery from the OTA .zip itself.
It was with me & I was searching for the solution.
jithumon said:
It was the stock recovery from king doing the problem.
I found the stock Indian recovery from the OTA .zip itself.
It was with me & I was searching for the solution.
Click to expand...
Click to collapse
Even after having flashd the recovery from the OTA update zip, I face an error - "unexpected content in build.prop"
Any ideas how to go about it???
spatone said:
Even after having flashd the recovery from the OTA update zip, I face an error - "unexpected content in build.prop"
Any ideas how to go about it???
Click to expand...
Click to collapse
Have you edited that??
Try to get build.prop from my backup...
(backup your current rom>flash my backup>copy build.prop > reflash your backup >replace the build.prop with the copied one) . I'm on 1.58, that's why I'm not giving mine.
jithumon said:
Have you edited that??
Try to get build.prop from my backup...
(backup your current rom>flash my backup>copy build.prop > reflash your backup >replace the build.prop with the copied one) . I'm on 1.58, that's why I'm not giving mine.
Click to expand...
Click to collapse
I havent modified a single line in build.prop file, and I already am using your 1.50 ROM backup from your thread, so I guess I will skip the 1.58 update and wait for the next update in your thread
The D816 keeps throwing newer problems time and again....anyways thanks for maintaining that thread!
spatone said:
I havent modified a single line in build.prop file, and I already am using your 1.50 ROM backup from your thread, so I guess I will skip the 1.58 update and wait for the next update in your thread
The D816 keeps throwing newer problems time and again....anyways thanks for maintaining that thread!
Click to expand...
Click to collapse
Yeah bro.... Now its having a lagging problem in 1.58.....I'm not experiencing it...but whoever flashed my latest backup is reporting lag.
Me too waiting for the next update.
I have stock rom android 4.4.2 on my galaxy mini s4. I have flashed a custom recovery CWM. and my phone is rooted. When i try to flash custom rom like CM13. or any other rom it gives a status 7 error and stops flashing the rom. Can someone provide me with a solution?
Hi you have to install TWRP recovery to flash the latest roms!
Argenis_jbc said:
Hi you have to install TWRP recovery to flash the latest roms!
Click to expand...
Click to collapse
I have installed allready TWRP recovery. version = recovery-twrp-2.6.3.0-serranoltexx.tar.md5
But still no good, getting the same error 7. Any other Solutions?
serti6610 said:
I have installed allready TWRP recovery. version = recovery-twrp-2.6.3.0-serranoltexx.tar.md5
But still no good, getting the same error 7. Any other Solutions?
Click to expand...
Click to collapse
Man you have to install the latest version, that is 3.0.x.x, here is the link http://forum.xda-developers.com/showthread.php?t=2678420
then you will can to flash any custom rom
Argenis_jbc said:
Man you have to install the latest version, that is 3.0.x.x, here is the link http://forum.xda-developers.com/showthread.php?t=2678420
then you will can to flash any custom rom
Click to expand...
Click to collapse
Thankyou sir, I will try it today. And I hope that it works.:fingers-crossed:
Argenis_jbc said:
Man you have to install the latest version, that is 3.0.x.x, here is the link http://forum.xda-developers.com/showthread.php?t=2678420
then you will can to flash any custom rom
Click to expand...
Click to collapse
I have flashed the recovery that you said it will work. But again it gives the same error. I am on stock android 4.4.2. Could that be the reason why it does not work?
serti6610 said:
I have flashed the recovery that you said it will work. But again it gives the same error. I am on stock android 4.4.2. Could that be the reason why it does not work?
Click to expand...
Click to collapse
Do you wipe in the correct way? Wipe data, system, cache? And not, this is not the problem
Argenis_jbc said:
Do you wipe in the correct way? Wipe data, system, cache? And not, this is not the problem
Click to expand...
Click to collapse
Yes I do wipe correct way. But error is still showing
Are you sure tu be on twrp recovery? Do you see the logo "twrqp" when you boot into reocovery? Sorry for the questions but when you said me the file name you wrote ".md5" and if i m correct you can' t flash an md5 file, you can flash only files that ends with ".tar", did you follow the twrp installation? Did you flashed the recovery with odin?
Argenis_jbc said:
Are you sure tu be on twrp recovery? Do you see the logo "twrqp" when you boot into reocovery? Sorry for the questions but when you said me the file name you wrote ".md5" and if i m correct you can' t flash an md5 file, you can flash only files that ends with ".tar", did you follow the twrp installation? Did you flashed the recovery with odin?
Click to expand...
Click to collapse
Yes I am sure because it shows the logo TWRP when starting recovery. Yes you cant flash md5 but thats not what i mean. Sorry for bad english. I have installed md5 with odin after flashed twrp as recovery.
One another thing is i have read on xda other threads that it could be de 'Assers lines" in the Updater script. Many people have fixed it like that but I dont know when lines I should erase in the Updater Script of the ending symbol of the Assets lines. Maybe you can help me with editing the Updater Script?
Disable the toggle firmature signed feature(CWM)
DarkJoker360 said:
Disable the toggle firmature signed feature(CWM)
Click to expand...
Click to collapse
I have tryed it but no good
serti6610 said:
I have tryed it but no good
Click to expand...
Click to collapse
Try to download cm 13 from your phone
Inviato dal mio GT-I9195 utilizzando Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the picture of the error 7.
maybe your zip file is corrupted, try downloading again. And its maybe annoying to repeat the same question. but have you done factory wipe?
I am trying to update my OP11. I follow the guide and what it says to do but my updates still fail at 59%. Anyone have any idea how to update it easy? I don't feel like rerooting it every update.
cabagekiller said:
I am trying to update my OP11. I follow the guide and what it says to do but my updates still fail at 59%. Anyone have any idea how to update it easy? I don't feel like rerooting it every update.
Click to expand...
Click to collapse
Update with Magisk installed? Did you restore the stock boot.img before updating?
WoKoschekk said:
Update with Magisk installed? Did you restore the stock boot.img before updating?
Click to expand...
Click to collapse
Yes I did. I don't reboot the device when I do it do I?
cabagekiller said:
Yes I did. I don't reboot the device when I do it do I?
Click to expand...
Click to collapse
No, do not reboot. But grab some logs from logcat and dmesg (kernel log) after update process fails. You just need the last lines when you grab it right after the error message.
1. Start update process
2. As soon as it fails open a terminal app and execute
Code:
logcat > /sdcard/logcat.txt
dmesg > /sdcard/kernel.txt
3. Find the logs in your intenal storage and have a look at the last lines of it.
You need to execute those commands as root (su).
cabagekiller said:
I am trying to update my OP11. I follow the guide and what it says to do but my updates still fail at 59%. Anyone have any idea how to update it easy? I don't feel like rerooting it every update.
Click to expand...
Click to collapse
you download stable full package in oxygen updater than flash with local updater apk.
sefai77 said:
you download stable full package in oxygen updater than flash with local updater apk.
Click to expand...
Click to collapse
Us have no full pack
ChrisFeiveel84 said:
Us have no full pack
Click to expand...
Click to collapse
But the updated firmware images on your device. Extract and upload them for other users, so they could be flashed on their devices to the inactive slot via fastboot. To know which partitions are needed you could extract a payload.bin of a full rom OTA update in other countries.
WoKoschekk said:
But the updated firmware images on your device. Extract and upload them for other users, so they could be flashed on their devices to the inactive slot via fastboot. To know which partitions are needed you could extract a payload.bin of a full rom OTA update in other countries.
Click to expand...
Click to collapse
Will Not work he have an usa model and the usa inrcemantal Update will fail when he have eu full rom on his phone
ChrisFeiveel84 said:
Will Not work he have an usa model and the usa inrcemantal Update will fail when he have eu full rom on his phone
Click to expand...
Click to collapse
I guess, there should be at least one user in the OP 11 forum here at XDA with a successful installed OTA update for US region. On this device you have the fully updated entire firmware images, that can be copied, uploaded and flashed on all the other devices that are not able to load the incremental OTA update due to root.
I was shown this picture,, what does this issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IronSkillet said:
I was shown this picture,, what does this issue?
View attachment 5866531
Click to expand...
Click to collapse
in the photo it looks like it couldn't download otas if you look at this (that's not a real rom name)
or an extra rom that is not intended for everyone " don't take it too seriously ")
How would he get rid of the problem?
This guy insisted the phone is broken..
I just want to point out a solution for the issue
IronSkillet said:
How would he get rid of the problem?
This guy insisted the phone is broken..
I just want to point out a solution for the issue
Click to expand...
Click to collapse
Is this a china op11 with oos on it ?
Yes, I guess he also had A_07 when he received the phone
I had used OxygenUpdater and it had no issues going A_08 ,
IronSkillet said:
Yes,
Click to expand...
Click to collapse
Than you have to download the rom and flash it over fastbootd and than flash the cos image back (only oplusstanvbk.img needed from cos 13 a10 build)
Ok,. Do you know a reputable community member who could do this process for him via remote support?
IronSkillet said:
Ok,. Do you know a reputable community member who could do this process for him via remote support?
Click to expand...
Click to collapse
Youtube video
Is easy to flash a phone with fbe and fasbootd and than flash thr the image from coloros oplusstanvbk.img
To the oplusstanvbk partition and reboot
He somehow doesn't want to make any effort in understanding the phone...
Anyone who can do this for him?
IronSkillet said:
He somehow doesn't want to make any effort in understanding the phone...
Anyone who can do this for him?
Click to expand...
Click to collapse
This he have to make for all Updates