Hi Guys,
I am looking for the 4.19.161.2 RUU for Vodafone UK (VODAP001) , I downloaded one from here but it doesn't launch.
Can anyone help? I have reverted my phone with the 4.19.161.2 nandroid and restored the 4.19.161.2 recovery, i went to do an OTA update and it fails so if someone could help that would be great.
Kind regards
Jamie
Here is an image of what happens when i look at the ota update log
{
"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"
}
montythebrave said:
Here is an image of what happens when i look at the ota update log
Click to expand...
Click to collapse
That usually means you have the wrong stock nandroid, or the wrong stock recovery.
What does it say for OS number on your bootloader screen?
redpoint73 said:
That usually means you have the wrong stock nandroid, or the wrong stock recovery.
What does it say for OS number on your bootloader screen?
Click to expand...
Click to collapse
Oh shoot! really?
Does this image help?
montythebrave said:
Oh shoot! really?
Click to expand...
Click to collapse
That is usually what the "fingerprint" error message means, yes.
But in your case, it looks like you properly matched the stock nandroid and stock recovery to your OS (main version) number. I know that probably seemed like a stupid question (that you properly matched those). But you never know, sometimes it pays to check the seemingly obvious stuff first.
So this is the OTA update that was automatically downloaded to your phone when you checked for an update in Settings? Or did you load it manually?
redpoint73 said:
That is usually what the "fingerprint" error message means, yes.
But in your case, it looks like you properly matched the stock nandroid and stock recovery to your OS (main version) number. I know that probably seemed like a stupid question (that you properly matched those). But you never know, sometimes it pays to check the seemingly obvious stuff first.
So this is the OTA update that was automatically downloaded to your phone when you checked for an update in Settings? Or did you load it manually?
Click to expand...
Click to collapse
Yeah I was 100% sure everything matched, thi is just the OTA update it automatically downloaded and tried to install through the settings menu.
montythebrave said:
Yeah I was 100% sure everything matched, thi is just the OTA update it automatically downloaded and tried to install through the settings menu.
Click to expand...
Click to collapse
That's odd, I don't see why the OTA is failing then. Software says "Official" on the bootloader screen?
You might also try the stock nandroid and stock recovery files for 4.19.161.3. Again, you properly matched the OS number (and .3 actually doesn't match). But I don't think it hurts anything to try.
redpoint73 said:
That's odd, I don't see why the OTA is failing then. Software says "Official" on the bootloader screen?
You might also try the stock nandroid and stock recovery files for 4.19.161.3. Again, you properly matched the OS number (and .3 actually doesn't match). But I don't think it hurts anything to try.
Click to expand...
Click to collapse
But if it doesnt match isint this a waste of time?
I was really looking for the RUU file so I can 100% put it back to stock.
montythebrave said:
But if it doesnt match isint this a waste of time?
Click to expand...
Click to collapse
Not necessarily. Sometimes the files will work, when the numbers are that close together.
I don't know of or have access to the RUU for your version number, so I'm trying to think out of the box here.
montythebrave said:
Here is an image of what happens when i look at the ota update log
View attachment 3668710
Click to expand...
Click to collapse
redpoint73 said:
Not necessarily. Sometimes the files will work, when the numbers are that close together.
I don't know of or have access to the RUU for your version number, so I'm trying to think out of the box here.
Click to expand...
Click to collapse
His mistake is wrong recovery version. He is using the old KitKat recovery 2.22.161.6 to update 4.19.161.2 to 4.19.161.3
The error clearly stated "this device has htc/vodafone_uk/htc_m8:4.4.3/KTUL84L" recovery image
but the expected recovery is htc/vodafone_uk/htc_m8:5.0.1/LRX22C
ckpv5 said:
His mistake is wrong recovery version. He is using the old KitKat recovery 2.22.161.6 to update 4.19.161.2 to 4.19.161.3
The error clearly stated "this device has htc/vodafone_uk/htc_m8:4.4.3/KTUL84L" recovery image
but the expected recovery is htc/vodafone_uk/htc_m8:5.0.1/LRX22C
Click to expand...
Click to collapse
Aaaah ok so which recovery should i install? I appreciate your help
montythebrave said:
Aaaah ok so which recovery should i install? I appreciate your help
Click to expand...
Click to collapse
As written above, you need to install either 4.19.161.2 or 4.19.161.3 stock recovery image as you're updating from 4.19.161.2 to 4.19.161.3
ckpv5 said:
As written above, you need to install either 4.19.161.2 or 4.19.161.3 stock recovery image as you're updating from 4.19.161.2 to 4.19.161.3
Click to expand...
Click to collapse
I downloaded a link on this forum which said it was the 4.19.161.2 stock recovery but it must of been incorrect, do you have a link for it?
Kind Regards
Jamie
ckpv5 said:
As written above, you need to install either 4.19.161.2 or 4.19.161.3 stock recovery image as you're updating from 4.19.161.2 to 4.19.161.3
Click to expand...
Click to collapse
I just found this - http://forum.xda-developers.com/showthread.php?p=62516597#post62516597 and downloaded and flashed 4.19.161.3 recovery: https://mega.nz/#!3U8hmQBT!nxY_ZG-5P...Sy8VZ7VtazWFzw
It all seemed to update fine now, thank you so much for your help!
I have 1 last problem, i have the supersu installer on my phone and i want to remove it, how do I go about doing that?
Infact, the update hasnt went very well....
it boots up the htc splash screen then it goes to a black screen and nothing... its went from bad to worse , any suggestions?
I managed to get into the the recovery log, here is what it reports (i took the sd card out to see if it would boot without it in case this was causing it to fail to load)
You can't use a rooted ROM to OTA.
You need a non-rooted ROM for that.
Read and everything that you need is linked in my signature.
Restore 4.19.161.2 backup and its stock recovery then try again.
I can't always reply because I'm on holiday in Krabi, Thailand.
I have only 50mb free data daily.
ckpv5 said:
You can't use a rooted ROM to OTA.
You need a non-rooted ROM for that.
Read and everything that you need is linked in my signature.
Restore 4.19.161.2 backup and its stock recovery then try again.
I can't always reply because I'm on holiday in Krabi, Thailand.
I have only 50mb free data daily.
Click to expand...
Click to collapse
When I create a backup with the latest TWRP it says successful, i then reboot into recovery again and mount data and i see the twrp folder but when i go into it, it is blank.
Related
HTC One X cid e11 Holland.
First got the small update, installed fine.. now jb, it doesn't work it shows the install progress with the robot and then it stops goes into clockwork and says something about the SD and reboots itself?
Unlocked, rooted and google now for ics
Anyone has the stock recovery?
Here's a pic , maybe this helps
{
"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"
}
Send from my HTC One X using TapTalk
Install the stock recovery. Then retry installing the ota update.
Do you have a link for me, please? And how to install it?
Send from my HTC One X using TapTalk
What is your stock base version ? (you can extract it from your RUU's, rom.zip)
and you install it from fastboot : fastboot flash recovery C:/....recovery.img
Vcek said:
What is your stock base version ? (you can extract it from your RUU's, rom.zip)
and you install it from fastboot : fastboot flash recovery C:/....recovery.img
Click to expand...
Click to collapse
Thanks for your help, to be honest I have no idea how to do that, I just installed the little update before jellybean, that went fine.. I don't know how to ?
Send from my HTC One X using TapTalk
ok, download this zip and extract it,
hold volume down and powerbutton until in bootloader
select fastboot with power button
connect usb
open the check_versions.bat file in the extracted folder
tell me what the check_versions told you
Vcek said:
ok, download this zip and extract it,
hold volume down and powerbutton until in bootloader
select fastboot with power button
connect usb
open the check_versions.bat file in the extracted folder
tell me what the check_versions told you
Click to expand...
Click to collapse
I hope this is correctly done :
Yes, hold on.
EDIT:
Download these 4 files: 1 2 3 4, and put them in the same Vtools folder.
get back to fastboot mode
run stock_recovery.bat
Try to install the OTA.
If it worked, restore CWM with cwm.bat
if it didn't work, also restore cwm until you find the stock recovery for your phone.
JB update needs a pure stock ROM with all stock apps and files intact.
It is best to revert to stock then only update to JB.
You need 2.17.401.2 RUU to revert.
ckpv5 said:
JB update needs a pure stock ROM with all stock apps and files intact.
It is best to revert to stock then only update to JB.
You need 2.17.401.2 RUU to revert.
Click to expand...
Click to collapse
So that I have google now for ICS I can't update whatever I try?
Doubt that
Vcek said:
Yes, hold on.
EDIT:
Download these 4 files: 1 2 3 4, and put them in the same Vtools folder.
get back to fastboot mode
run stock_recovery.bat
Try to install the OTA.
If it worked, restore CWM with cwm.bat
if it didn't work, also restore cwm until you find the stock recovery for your phone.
Click to expand...
Click to collapse
Thank you, doing it now
siemz said:
So that I have google now for ICS I can't update whatever I try?
Doubt that
Click to expand...
Click to collapse
The OTA will look for the original Google Search apk to patch, if it can't find it, the OTA will fails. Same for other apks.
Anyway, you can try the OTA update first and see how it goes. If it fails, your only option is RUU to revert to stock.
ckpv5 said:
The OTA will look for the original Google Search apk to patch, if it can't find it, the OTA will fails. Same for other apks.
Anyway, you can try the OTA update first and see how it goes. If it fails, your only option is RUU to revert to stock.
Click to expand...
Click to collapse
it indeed shows a red error sign now next to the phone
And can't I just restore an original copy of the google APK?
or delete it ?
And where could I find one?
The red error sign is right above when it's half done installing then stops, rebooted my phone now
siemz said:
it indeed shows a red error sign now next to the phone
And can't I just restore an original copy of the google APK?
or delete it ?
Click to expand...
Click to collapse
You need to restore the original apk, not delete it... same thing for other apks that you may have already removed or disabled (you need to re-enable them).
Also root must be removed, but not too sure whether OTA updating will be successful with an unlocked bootloader as this is a major update.
As I said earlier, it is best to revert to stock first with a RUU for a hassle free JB update, but you lose all the settings and customization.
ckpv5 said:
You need to restore the original apk, not delete it... same thing for other apks that you may have already removed or disabled (you need to re-enable them).
Also root must be removed, but not too sure whether OTA updating will be successful with an unlocked bootloader as this is a major update.
As I said earlier, it is best to revert to stock first with a RUU for a hassle free JB update, but you lose all the settings and customization.
Click to expand...
Click to collapse
Where could I find the original google search APK? That's the only thing I really used when was rooted,
And I heard bout successful updates when unlocked + Rooted
please, anyone provide the official google search apk
siemz said:
Where could I find the original google search APK? That's the only thing I really used when was rooted,
And I heard bout successful updates when unlocked + Rooted
please, anyone provide the official google search apk
Click to expand...
Click to collapse
Here are the GoogleQuickSearchBox.apk and GoogleQuickSearchBox.odex from 2.17.401.2
Thanks!
trying it now
ckpv5 said:
Here are the GoogleQuickSearchBox.apk and GoogleQuickSearchBox.odex from 2.17.401.2
Click to expand...
Click to collapse
What is the odex for
moved both into /system/app rebooting now then trying to update
siemz said:
What is the odex for
Click to expand...
Click to collapse
I just put there in case you removed the odex file too. If it is still there, then it is ok. Hmm... stock ROM comprise of apk + odex files.
ckpv5 said:
I just put there in case you removed the odex file too. If it is still there, then it is ok. Hmm... stock ROM comprise of apk + odex files.
Click to expand...
Click to collapse
Update is redownloading now, thanks for your help
Hope this works :angel:
hi there, i have a problem while trying too root my s3 using ct-autoroot.
after connecting and flashing it via odin everything goes smooth and fine but when it restarts my phone it won't boot into recovery it would only flash black screen with a blue font in the top saying "recovery booting..." then shut it self down. I watched some other video on youtube which their phone successfully boot into recovery->blackscreen->samsung->logo->recovery thats installing the new file from autoroot, but mine just doesnt work even if i clear the cache and tried to redo the steps, still gets "recovery booting" ->black screen->phone shutsdown
it was also stated on the chainfire autoroot website that
"For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually."
i have Samsung s3 (sgh-i747m)
carrier: bell
Android version: 4.1.2
P.s
I also tried installing root checker and tried to check my system but it says : "Sorry root access is not properly installed on this device"
Do you have any warranty left on your phone? Is your phone sim unlocked?
Since you're on 4.1.2, you can unlock your phone using the free method.
audit13 said:
Do you have any warranty left on your phone? Is your phone sim unlocked?
Since you're on 4.1.2, you can unlock your phone using the free method.
Click to expand...
Click to collapse
thank you for answering i really appreciate it btw my phone is already sim unlocked and its already a year or two since the warranty expired
Did you solve the problem?
audit13 said:
Did you solve the problem?
Click to expand...
Click to collapse
nope, problem is still happening what i mean is its already sim unlocked before i tried to root. it still shuts down completely when trying to boot into recovery mode when flashing cf-autoroot for sgh-i747m
The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.
audit13 said:
The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.
Click to expand...
Click to collapse
ok thanks for answering ill try it
audit13 said:
The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.
Click to expand...
Click to collapse
one question sir audit. will it be safe to flash a stock rom? i mean what if it fails to boot into recovery again. will it bricked my phone if that happens?
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
hi , i successfully flashed 4.3 stock rom (because i cant find a 4.1.2 stock rom) what i noticed is the app called knox. i heard that it sometimes block you from rooting your phone. but when i clicked on it ,it ask me if i want to install it which is approximately 119mb of data but i havent clicked on it yet. I also check if its in my device security administration but it is not currently checked. Is it still safe to root my s3?
yves010598 said:
hi , i successfully flashed 4.3 stock rom (because i cant find a 4.1.2 stock rom) what i noticed is the app called knox. i heard that it sometimes block you from rooting your phone. but when i clicked on it ,it ask me if i want to install it which is approximately 119mb of data but i havent clicked on it yet. I also check if its in my device security administration but it is not currently checked. Is it still safe to root my s3?
Click to expand...
Click to collapse
audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
Nevermind i already did it. i successfully rooted my device thanks a lot for helping me i can only show my gratitude my pressing the "thanks" button i hope its enough to thank you
If you update to the latest kk, the easiest way to root would be to flash a custom recovery and flash supersu via recovery.
audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
is it fine to flash d2lte even thou my phone is a canadian version (bell carrier)
here's a screenshot
{
"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"
}
yves010598 said:
is it fine to flash d2lte even thou my phone is a canadian version (bell carrier)
here's a screenshot
Click to expand...
Click to collapse
d2lte is the unified version. you should be a.o.k.
"all i can really do , is stay out of my own way and let the will of heaven be done"
audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
mrrocketdog said:
d2lte is the unified version. you should be a.o.k.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
thank you mrrocketdog and mraudit13 i only got a few knowledge about android stuffs. I already pressed thanks for your replies thank you
If phone screen isnt working how to flash
audit13 said:
The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.
Click to expand...
Click to collapse
HI there, same problem I am facing as well. How to flash the stock ROM and recovery if the screen is not working? ODIN is not recognizing the device. No SD card as well.
My Galaxy S3 is SIM locked and with Bell .. Android 4.4.2 How to go back to normal mode again ? Thx.
Removed battery for a min, changed the USB port on the computer and attempted the process for about 5 times- then Volume down + Power + centre home button- started ODIN- recovery image was there as well.- flashed- Back to normal.. Sigh !
If you can't see the screen, the easiest way to get to download mode would be to use a USB jig. I purchased a jig soon after getting my Samsung Captivate. It has been used by me and several frieds to get ourselves out of a jam.
Hi all. My daughter has been using my s3. I wanted to restore back to stock with Odin so i can update the phone for her. I've don't it so many times in the past without issue. Tonight I tries a few times. All goes well with Odin. No issues no errors. Yet when it finishes it boots right back up and nothing was actually done. Phone is same as it was. The phone was actually not restored to stock. What am I missing?
Is the phone an i747 or i747m? What bootloader is on the phone?
audit13 said:
is the phone an i747 or i747m? What bootloader is on the phone?
Click to expand...
Click to collapse
i747. Ucdlk3.
When I go software update it doesn't do anything. It's rooted with custom recovery. So wanted to just go stock and then update.
You're flashing the phone using the stock firmware from sammobile? What version of desktop Odin are you using?
audit13 said:
You're flashing the phone using the stock firmware from sammobile? What version of desktop Odin are you using?
Click to expand...
Click to collapse
Odin is 3.06
Using the same file I've always used. Root_art_i747ucdlk3.tar.md5
Its just strange as odin looks good and it passes at the end. Think its worth into try re-downloading the firmware? These files and the version of odin are what I've always used. And its the USB cable that came with the phone. Computer recognizes the phone too.
Post a screenshot of the Odin progress. Are you unchecking everything except F.reset time and auto reboot?
audit13 said:
Post a screenshot of the Odin progress. Are you unchecking everything except F.reset time and auto reboot?
Click to expand...
Click to collapse
Correct. Those are the only two options that are checked. I'll try again and try and get pics. I know the first 2 times after odin was done it said "reset". The next two times it said "pass"
Try re-flashing using rom from sammobile.com. You need a completely stock rom in order to install ota updates.
audit13 said:
Try re-flashing using rom from sammobile.com. You need a completely stock rom in order to install ota updates.
Click to expand...
Click to collapse
Thanks for the replies and help. I'm gonna give that a shot.
Update. Same result.
{
"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"
}
I have the LK3 tar file. I can upload it to my Drive account and give you access to download it if you want. PM me your email address
Try Odin 3.07. Weird that I see i9505 on the Odin screen.
Boot into download mode and let us know what is says on the screen.
audit13 said:
Try Odin 3.07. Weird that I see i9505 on the Odin screen.
Boot into download mode and let us know what is says on the screen.
Click to expand...
Click to collapse
Thanks. Download mode says model is sgh-i747.
That's good. As I said, try Odin 3.07 which is what I always use. When flashing, this is what I do:
Launch Odin, uncheck everything except f.reset time, flash. When I see the word reset in the status window, remove, the usb cable, remove battery, replace battery, boot into recovery, do a factory reset/wipe, boot phone.
audit13 said:
Try Odin 3.07. Weird that I see i9505 on the Odin screen.
Boot into download mode and let us know what is says on the screen.
Click to expand...
Click to collapse
Similar issues as OP, trying to go back to stock and having no success.
Anybody have a good tar stock rom link I can use?
On CWM Recovery and Cyanogenmod 11, bad flash caused me to lose IMEI. Yeah I'm in a world of hurt here.
Attempting to download firmware from sammobile right now. I've tried many things and all failed.
fausto412 said:
Similar issues as OP, trying to go back to stock and having no success.
Anybody have a good tar stock rom link I can use?
On CWM Recovery and Cyanogenmod 11, bad flash caused me to lose IMEI. Yeah I'm in a world of hurt here.
Attempting to download firmware from sammobile right now. I've tried many things and all failed.
Click to expand...
Click to collapse
Before flashing anything from sammobile, make sure you are now running a 4.3 or newer bootloader. Flashing a ROM from sammobile with a 4.3 or newer bootloader might bright your phone.
audit13 said:
Before flashing anything from sammobile, make sure you are now running a 4.3 or newer bootloader. Flashing a ROM from sammobile with a 4.3 or newer bootloader might bright your phone.
Click to expand...
Click to collapse
How do I figure out what bootloader I have? I was on Cyanogenmod 11.
I tried to flash the sammobile firmware and it wouldn't flash. so no harm done there.
I want to recover my IMEI number and apparently t do tyhat you need to go back to stock so here I am.
fausto412 said:
How do I figure out what bootloader I have? I was on Cyanogenmod 11.
I tried to flash the sammobile firmware and it wouldn't flash. so no harm done there.
I want to recover my IMEI number and apparently t do tyhat you need to go back to stock so here I am.
Click to expand...
Click to collapse
If you want an easy way just install Root Checker by Free Android Tools. It's free will give you all the info you need.
I won't be able to try out again until this weekend. But this is just driving me crazy. I have a folder with Odin and my stock file that I have had and used forever. Never had an issue. Just did this a few months ago when I did this to get the phone ready before I have it to her. No idea what's going on.
fausto412 said:
Similar issues as OP, trying to go back to stock and having no success.
Anybody have a good tar stock rom link I can use?
On CWM Recovery and Cyanogenmod 11, bad flash caused me to lose IMEI. Yeah I'm in a world of hurt here.
Attempting to download firmware from sammobile right now. I've tried many things and all failed.
Click to expand...
Click to collapse
Any luck?
Me again!! Sorry for spamming but i need little help here
I have an M8x unlocked version (CID no. HTC__621), S-ON, Rooted. Yesterday pop-up OTA update (number 4.24.709.3). My phone running Lollipop 5.0.2 (4.24.709.2). The phone must be "stock" to do an OTA, so i install the stock recovery (i understand the stock recovery this and is here). Once i do that i try to install OTA and the desaster come, my phone run into bootloop (stucked in htc logo) then i remember the backup i do before, so phone is now operating. the thing, i know, with root i can't install any update, so i want to go back into pure stock sense, with stock recovery to do the update, or at least come back to one version that allow make the OTA's (Android M is coming!!!) i'm a little dumb haha, i need some good soul to teach me exactly what to do to finally leave my phone alone and you guys, thank you so much 4 help me out!! (sorry for my bad english)
HTC One M8x
CID No. HTC__621
Firmware No. 4.24.709.2
Bootloader Unlocked
Factory Unlocked
Rooted
Custom Recovery TWRP
Meliragazza2571 said:
Me again!! Sorry for spamming but i need little help here
I have an M8x unlocked version (CID no. HTC__621), S-ON, Rooted. Yesterday pop-up OTA update (number 4.24.709.3). My phone running Lollipop 5.0.2 (4.24.709.2). The phone must be "stock" to do an OTA, so i install the stock recovery (i understand the stock recovery this and is here). Once i do that i try to install OTA and the desaster come, my phone run into bootloop (stucked in htc logo) then i remember the backup i do before, so phone is now operating. the thing, i know, with root i can't install any update, so i want to go back into pure stock sense, with stock recovery to do the update, or at least come back to one version that allow make the OTA's (Android M is coming!!!) i'm a little dumb haha, i need some good soul to teach me exactly what to do to finally leave my phone alone and you guys, thank you so much 4 help me out!! (sorry for my bad english)
HTC One M8x
CID No. HTC__621
Firmware No. 4.24.709.2
Bootloader Unlocked
Factory Unlocked
Rooted
Custom Recovery TWRP
Click to expand...
Click to collapse
You cannot take an OTA if you are rooted, have custom recovery. You MUST be absolutely stock ROM with stock recovery to take and install correctly OTA updates.
similar problem.. i flashed stock recovery but still getting installation aborted..
{
"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"
}
mushfiq20 said:
similar problem.. i flashed stock recovery but still getting installation aborted..
Click to expand...
Click to collapse
You can't even update if you "unrooted" your rom.
You must have NEVER rooted stock rom + recovery !
mushfiq20 said:
similar problem.. i flashed stock recovery but still getting installation aborted..
Click to expand...
Click to collapse
It's clearly shown in the log you have a rooted device or a unrooted previously rooted device, your binary is not stock
ckpv5 said:
It's clearly shown in the log you have a rooted device or a unrooted previously rooted device, your binary is not stock
Click to expand...
Click to collapse
so now what can i do if i want to update??
mushfiq20 said:
so now what can i do if i want to update??
Click to expand...
Click to collapse
Like i said, you need a never rooted stock backup. You should have made one after you flashed twrp to begin with.
But go to the backup threads and find the one that corresponds with your software build number. Restore it and flash the stock recovery. Then you can do ota
Had the same problem
I just wanted to share my experience. I had the same problem.
So I downloaded a twrp-backup of my version, since I failed to do proper backups myself. Then I unpacked it. The system.ext4.win### can be unpacked with tar.
Then I did a: (on my linux, but should work with cygwin for windows. It gives a list of the checksum of all files under the current directory)
find . -type f -exec md5sum {} \; > stock.md5
Uploaded the stock.m5 and compared to my phones files. md5sum -c stock.md5 works if you have it installed, if not, can make a script that uses the md5-command.
What I found in this OTA for me, was that my /system/bin/app_process32 was softlinked to /system/xbin/daemonsu, and thus had the wrong md5sum.
The original was saved, so I booted twrp and adb in to restore the file.
After that the OTA would run, and all looked good, until it rebooted, and got stuck at the boot-screen. Did the hold volume-up and power to reboot into bootloader. (Did it a few times before I read online that you must unplug the usb for it to work)
My OS was the new version (6.12.709.4), so it seemed as the important parts were updated right. I searched for a backup in the recovery-thread, but there was none yet.
After that fastboot boot twrp.img, to start it without flashing. And then did a full backup of phone again, and now unpacked my backup. Just looking through to see if any other softlink was wrong, I found that /system/bin/app_process had changed to also softlink to /system/xbin/daemonsu. (It was softlinked to app_process32 before...)
So I cd /system/xbin/ && rm app_process && ln -s app_process32 app_process
Then I rebooted, and now my phone is working great with android version 6.0.
Im not saying anyone should do like this. I just telling this for those who want to look around before flashing a binary downloaded from somewhere. So as per usual, dont blame me.
Mr Hofs said:
Like i said, you need a never rooted stock backup. You should have made one after you flashed twrp to begin with.
But go to the backup threads and find the one that corresponds with your software build number. Restore it and flash the stock recovery. Then you can do ota
Click to expand...
Click to collapse
I did as u said. from the backup thread i downloaded twrp backup of matching CID, restored it and flashed stock recovery and thn tried updating via OTA. but still no luck. is it happening because i career unlocked my phone?
mushfiq20 said:
I did as u said. from the backup thread i downloaded twrp backup of matching CID, restored it and flashed stock recovery and thn tried updating via OTA. but still no luck. is it happening because i career unlocked my phone?
Click to expand...
Click to collapse
Carrier unlocking has nothing to do with the OTA. As long as the firmware, ROM and stock recovery all match, there's no reason why you cannot take OTA updates. If you are rooted, however, you cannot take the updates, they will fail to install.
Einwod said:
Carrier unlocking has nothing to do with the OTA. As long as the firmware, ROM and stock recovery all match, there's no reason why you cannot take OTA updates. If you are rooted, however, you cannot take the updates, they will fail to install.
Click to expand...
Click to collapse
all the roms of the backup thread are non-rooted stock roms right? so it should have worked i guess.. but it didn't. is there any way to directly flash marshmallow sense stock rom? i found thread for GPE edition but didnt find any for sense edition. my CID is BM____001 btw...
Meliragazza2571 said:
Me again!! Sorry for spamming but i need little help here
I have an M8x unlocked version (CID no. HTC__621), S-ON, Rooted. Yesterday pop-up OTA update (number 4.24.709.3). My phone running Lollipop 5.0.2 (4.24.709.2). The phone must be "stock" to do an OTA, so i install the stock recovery (i understand the stock recovery this and is here). Once i do that i try to install OTA and the desaster come, my phone run into bootloop (stucked in htc logo) then i remember the backup i do before, so phone is now operating. the thing, i know, with root i can't install any update, so i want to go back into pure stock sense, with stock recovery to do the update, or at least come back to one version that allow make the OTA's (Android M is coming!!!) i'm a little dumb haha, i need some good soul to teach me exactly what to do to finally leave my phone alone and you guys, thank you so much 4 help me out!! (sorry for my bad english)
HTC One M8x
CID No. HTC__621
Firmware No. 4.24.709.2
Bootloader Unlocked
Factory Unlocked
Rooted
Custom Recovery TWRP
Click to expand...
Click to collapse
Have you solved your problem ? If not yet ... you can ask in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I'll help you because all your needed files are there.
I just checked all your 9 posts, seems like you not yet solve your problem
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
mushfiq20 said:
all the roms of the backup thread are non-rooted stock roms right? so it should have worked i guess.. but it didn't. is there any way to directly flash marshmallow sense stock rom? i found thread for GPE edition but didnt find any for sense edition. my CID is BM____001 btw...
Click to expand...
Click to collapse
Which backup that you restored ? You need 4.20.666.2 and I don't see anywhere that backup is posted.
ckpv5 said:
Have you solved your problem ? If not yet ... you can ask in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I'll help you because all your needed files are there.
I just checked all your 9 posts, seems like you not yet solve your problem
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
Which backup that you restored ? You need 4.20.666.2 and I don't see anywhere that backup is posted.
Click to expand...
Click to collapse
i restored this one.. https://www.androidfilehost.com/?fid=23578570567722629
i know this is not 4.20.666.2. but i thought if i could climb my way up to marshmallow from 1.55.666.4 by updating again and again.
mushfiq20 said:
i restored this one.. https://www.androidfilehost.com/?fid=23578570567722629
i know this is not 4.20.666.2. but i thought if i could climb my way up to marshmallow from 1.55.666.4 by updating again and again.
Click to expand...
Click to collapse
You can try. But I think the OTA will detect that the ROM number doesn't match your firmware number, and fail.
mushfiq20 said:
i restored this one.. https://www.androidfilehost.com/?fid=23578570567722629
i know this is not 4.20.666.2. but i thought if i could climb my way up to marshmallow from 1.55.666.4 by updating again and again.
Click to expand...
Click to collapse
That's too low version.
Have a look the thread linked in my signature. There's a non-rooted backup 3.34.666.4. Give me 5 minutes, I put up link for 4.20.666.1 so you do only 2 OTAs to Marshmallow - 4.20.666.1 --> 4.20.666.2 --> 6.13.666.7
If you're willing to wait, I can upload 4.20.666.2 tomorrow night as it is already late here and I need to go to bed soon. Make request in my thread so I don't forget (if this is needed)
Edit : Link for 4.20.666.1 updated
ckpv5 said:
That's too low version.
Have a look the thread linked in my signature. There's a non-rooted backup 3.34.666.4. Give me 5 minutes, I put up link for 4.20.666.1 so you do only 2 OTAs to Marshmallow - 4.20.666.1 --> 4.20.666.2 --> 6.13.666.7
If you're willing to wait, I can upload 4.20.666.2 tomorrow night as it is already late here and I need to go to bed soon. Make request in my thread so I don't forget (if this is needed)
Edit : Link for 4.20.666.1 updated
Click to expand...
Click to collapse
thank you so much. . i will have to flash it tomorrow anyway. but i guess 4.20.666.1 will be good enough. i dont have a problem with doing 2 OTA's
mushfiq20 said:
thank you so much. . i will have to flash it tomorrow anyway. so it would be great if you can upload 4.20.666.2 tomorrow. but 4.20.666.1 will do too.
Click to expand...
Click to collapse
Sure can .. but will be late night here after I come home from work (also my internet is not fast enough .. to upload a nandroid takes about 2-3 hrs)
ckpv5 said:
Sure can .. but will be late night here after I come home from work (also my internet is not fast enough .. to upload a nandroid takes about 2-3 hrs)
Click to expand...
Click to collapse
you dont have to go through the hassle. this version will do.. i just hope it works.
now this is weird.. i flashed 4.20.666.1 .. and when i check for software updates i get "There are no updates available for your phone." :/
mushfiq20 said:
now this is weird.. i flashed 4.20.666.1 .. and when i check for software updates i get "There are no updates available for your phone." :/
Click to expand...
Click to collapse
Keep your hair on and wait a while. It takes time sometimes for the updates to come through. You did flash the stock recovery as well?
Hello everyone i have those 2 errors in the title and i dont know how to solve them.
Any help?
Thanks in advance
qiodizjqdpiojqfioj said:
Hello everyone i have those 2 errors in the title and i dont know how to solve them.
Any help?
Thanks in advance
Click to expand...
Click to collapse
What did you do for that to happen?
Arm1nas said:
What did you do for that to happen?
Click to expand...
Click to collapse
i tried flashing my phone with "A528BXXU1BUL7"
qiodizjqdpiojqfioj said:
i tried flashing my phone with "A528BXXU1BUL7"
Click to expand...
Click to collapse
Did you only flash one slot with A528BXXU1BUL7 version? Because if the rest of the slots have an older version, it won't work. Every slot (AP, CSC, BL, etc) need to be flashed with the same firmware version.
Arm1nas said:
Did you only flash one slot with A528BXXU1BUL7 version? Because if the rest of the slots have an older version, it won't work. Every slot (AP, CSC, BL, etc) need to be flashed with the same firmware version.
Click to expand...
Click to collapse
i flashed all slots with the files it came with in the ZIP file
Arm1nas said:
Did you only flash one slot with A528BXXU1BUL7 version? Because if the rest of the slots have an older version, it won't work. Every slot (AP, CSC, BL, etc) need to be flashed with the same firmware version.
Click to expand...
Click to collapse
i just saw there is one bul6 file hidden in there
qiodizjqdpiojqfioj said:
i just saw there is one bul6 file hidden in there
Click to expand...
Click to collapse
Where did you download it from? Just download the latest firmware from samfw or sammobile
Arm1nas said:
Where did you download it from? Just download the latest firmware from samfw or sammobile
Click to expand...
Click to collapse
i tdownloaded it from samfw today and it still shows the same error.
i do have to mention i currently have android version 13 so it might be with me trying to downgrade
qiodizjqdpiojqfioj said:
i tdownloaded it from samfw today and it still shows the same error.
i do have to mention i currently have android version 13 so it might be with me trying to downgrade
Click to expand...
Click to collapse
Which files are you flashing? Everything? Or just AP?
You need to flash all of these files in their corresponding slots:
{
"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"
}
Arm1nas said:
Which files are you flashing? Everything? Or just AP?
You need to flash all of these files in their corresponding slots:
View attachment 5894001
Click to expand...
Click to collapse
i am flashing all of them in the correct order using odin3
qiodizjqdpiojqfioj said:
i am flashing all of them in the correct order using odin3
Click to expand...
Click to collapse
Does it immediately say "fail" in odin, or does it try to flash something first? Send some screenshots, photo of the download mode of the phone. Maybe redownloading the firmware again is worth a try, maybe it got corrupted or something.
Arm1nas said:
Does it immediately say "fail" in odin, or does it try to flash something first? Send some screenshots, photo of the download mode of the phone. Maybe redownloading the firmware again is worth a try, maybe it got corrupted or something.
Click to expand...
Click to collapse
hi i redownloaded the firmware and it worked yet now my phone is still in a boot loop any help?
qiodizjqdpiojqfioj said:
hi i redownloaded the firmware and it worked yet now my phone is still in a boot loop any help?
Click to expand...
Click to collapse
Maybe your phone battery is dead, then it boot loops like this, charge it for an hour, happened to me once.
Arm1nas said:
Maybe your phone battery is dead, then it boot loops like this, charge it for an hour, happened to me once.
Click to expand...
Click to collapse
i charged it still in bootloop
u have 3 bit binary u cant downgrade from a13
qiodizjqdpiojqfioj said:
Hello everyone i have those 2 errors in the title and i dont know how to solve them.
Any help?
Thanks in advance
Click to expand...
Click to collapse
You can't downgrade your device to an older OS version anymore since you've flashed/had installed a firmware with SW REV. 3, the error clearly explains that you're trying to flash a firmware with SW REV. 1. Flash the latest firwmare available to fix this issue.
BlackMesa123 said:
You can't downgrade your device to an older OS version anymore since you've flashed/had installed a firmware with SW REV. 3, the error clearly explains that you're trying to flash a firmware with SW REV. 1. Flash the latest firwmare available to fix this issue.
Click to expand...
Click to collapse
i flashed wth android version 13 again and its still stuck in a bootloop its charged and i can hard reset.
If i hard reset its stll stuck in a bootloop any help?
qiodizjqdpiojqfioj said:
i flashed wth android version 13 again and its still stuck in a bootloop its charged and i can hard reset.
If i hard reset its stll stuck in a bootloop any help?
Click to expand...
Click to collapse
Have you flashed all the BL+CP+AP+CSC (not HOME_CSC) tar packages via Odin3?
BlackMesa123 said:
Have you flashed all the BL+CP+AP+CSC (not HOME_CSC) tar packages via Odin3?
Click to expand...
Click to collapse
yes i did.
qiodizjqdpiojqfioj said:
yes i did.
Click to expand...
Click to collapse
Are you stuck on the splash screen (Samsung Galaxy logo) or is your phone in a bootloop (Samsung-only logo)? Have you also tried a Factory reset via recovery mode?