Related
Got an update notification last night for 3.14.531.17 (19.72 MB). I'm running Unknown's ROM 1.7.1 so I thought this was a bit strange. Has anyone else received this update?
Anyways, here's a link to the update file for anyone that's interested and intrepid enough to try it. https://www.dropbox.com/s/ajueet3ta...e_320853foljnqxv82dc62l1.zip.20263.enc?v=0mcn MD5: af450b9f70e14fd01798031e7c52228e
So far I have not run it. I am on CID: T-MOB010, S-OFF for anyone that's curious.
Your file is corrupted.
hasoon2000 said:
Your file is corrupted.
Click to expand...
Click to collapse
no its encrypted that is what the .enc at the end is.
mkinney88 said:
no its encrypted that is what the .enc at the end is.
Click to expand...
Click to collapse
Oh yeah. Forgot about that encryption crap that HTC has.
hasoon2000 said:
Oh yeah. Forgot about that encryption crap that HTC has.
Click to expand...
Click to collapse
can you remove the .enc from the ota.zip.enc cause i know there is a program to remove the encryption from RUU ROM01.zip but i don't know if it works on the OTA zips cause the RUU ROM01.ZIP that is encrypted doesn't have the .enc at the end.
mkinney88 said:
can you remove the .enc from the ota.zip.enc cause i know there is a program to remove the encryption from RUU ROM01.zip but i don't know if it works on the OTA zips cause the RUU ROM01.ZIP that is encrypted doesn't have the .enc at the end.
Click to expand...
Click to collapse
Just tried it right now actually and it says "Invalid HTC AES encrypted zip file". I'm not very familiar with Ubuntu but I have decrypted a few RUUs before, just not OTAs.
hasoon2000 said:
Your file is corrupted.
Click to expand...
Click to collapse
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
mongoosesRawesome said:
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
Click to expand...
Click to collapse
its not corrupted its just encrypted, ill keep trying to check for an update but i don't get anything. I even ran the RUU and still no dice??
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
mongoosesRawesome said:
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
Click to expand...
Click to collapse
i wonder if you try to run the update and when it reboot it will unencrypt it and before it errors out you and adb pull from a temp folder or something
---------- Post added at 03:46 PM ---------- Previous post was at 03:36 PM ----------
hasoon2000 said:
Just tried it right now actually and it says "Invalid HTC AES encrypted zip file". I'm not very familiar with Ubuntu but I have decrypted a few RUUs before, just not OTAs.
Click to expand...
Click to collapse
did you try and remove the .20263.enc off the end and try decrypting it
mkinney88 said:
its not corrupted its just encrypted, ill keep trying to check for an update but i don't get anything. I even ran the RUU and still no dice??
did you try and remove the .20263.enc off the end and try decrypting it
Click to expand...
Click to collapse
Yup. I'm thinking of ways to decrypt it
hasoon2000 said:
Yup. I'm thinking of ways to decrypt it
Click to expand...
Click to collapse
any new ideas?
mkinney88 said:
any new ideas?
Click to expand...
Click to collapse
I renamed it as update.zip and attempted to flash it. It failed. My One S is completely stock since I'm going to sell it. So it may be a bad download or something. Not too sure.
hasoon2000 said:
I renamed it as update.zip and attempted to flash it. It failed. My One S is completely stock since I'm going to sell it. So it may be a bad download or something. Not too sure.
Click to expand...
Click to collapse
It's definitely weird, I'll give you that. Especially since I haven't seen anyone else receive this update OTA. I just deleted, rechecked for updates, and it downloaded again, and I checked the MD5 with the previous file, and it matched, again, so we can rule out a bad download. Perhaps a bad source file.
MD5: af450b9f70e14fd01798031e7c52228e
What does the new update do?
Sent from my HTC VLE_U using xda app-developers app
Lionhardt said:
What does the new update do?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Since no one's been able to apply the update and it's not listed on the t-mobile website, who knows.
My phone is stock, but I haven't received this update. I'm guessing this is supposed to fix the battery drain from GPS always being on when wifi calling is enabled.
HTC has updated their ROM Update page with a 3.14.531.17 RUU.
HTC One S for T-Mobile ROM Update | 6.24.2013
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Anyone who's familiar with ruuveal want to take a crack at it?
I too am running unknown 1.7.1 and am getting an ota update that is 19mb. I as wondering if should run it.
---------- Post added at 08:00 PM ---------- Previous post was at 07:44 PM ----------
darrin976 said:
I too am running unknown 1.7.1 and am getting an ota update that is 19mb. I as wondering if should run it.
Click to expand...
Click to collapse
My file is named OTA_Ville_U_JB_45_S_TMOUS_3.14.531.17-3.14.531.11_release_320853foljnqxv82dc62l1.zip
You guys should upgrade to 1.8.1 here: http://forum.xda-developers.com/showthread.php?t=2250573
It contains the fixes for battery usage and wifi calling. If anything, I think it might be better than ICS. Now if I could only get Google Navigation to work properly in 3D mode (using Waze instead for now).
mongoosesRawesome said:
You guys should upgrade to 1.8.1 here: http://forum.xda-developers.com/showthread.php?t=2250573
It contains the fixes for battery usage and wifi calling. If anything, I think it might be better than ICS. Now if I could only get Google Navigation to work properly in 3D mode (using Waze instead for now).
Click to expand...
Click to collapse
I tried to yesterday unsuccessfully, I am going to try again soon.
Anyone know what will happen if I do this ota update?
The update you are referring to is going to be from T-mobile, so it will not work. What problems did you run into with the 1.8.1 update?
So i have a STOCK HTC_M8Wl and a while back I tried to update it and this happened. The phone is no longer activated I've wiped data and cache from recovery mode I can also get into bootloader mode. When I attempt to power on the phone it shows the HTC boot screen for a min then turns off and back on to the same screen and after a minute or two it goes to a black screen then displays the phone with a red triangle and exclamation point in the middle then stays there.
I've looked all around the Internet and found this problem commonly with rooted devices but my problem is that mines is not rooted and is 100% stock. Is there a way to fix this problem from my position please let me know because I would love to make a thread on this problem because I only found one and they never explained how to fix it. (I belive it was the problem as mines) also I don't know much about HTC phones I have worked with rooting android before.
My solution:
Thanks to izzaeroth and the thread he provided me I was able to revive my phone. The ruu zip file kept failing saying signature verification failed do to large img file. So I decided to try the 6.0 ruu exe file instead. (My pc does have drivers to detect the phone while it's in fastboot mode) I launched the exe and it extracted the ruu I plug in my phone and started the process. It flashed all partitions it did take a while to load but after the update the phone booted it began to optimize 226 apps after that it booted and done it finally was fixed.
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Click to expand...
Click to collapse
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
-spektor- said:
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
Click to expand...
Click to collapse
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Click to expand...
Click to collapse
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
-spektor- said:
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
Click to expand...
Click to collapse
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
It said it in fastboot when ever it detected the file n I think it said the same when i tried it with adb/fastboot on windows pc
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
-spektor- said:
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
Click to expand...
Click to collapse
awesome! glad u got it working
Hey everyone, I managed to download the OTA update bin file from FOTA server for the S8 Unlocked (US Version). If anyone is interested in testing and post the update I will leave the link to the OTA bin file. I am actually working on it as well. I am assuming it should be flashable as long as you have latest Nougat 7.0 for the unlocked S8 or if you have installed Unlocked firmware in your Carrier branded Galaxy S8. I will be doing some test as well but I need some rest before I start working on it again. Will keep you all posted and hope some of you guys would like to do some test with it. I am pretty sure we will figure out how to flash it.
As far as I know from last year you could flash update.zip file which was extracted from the Verizon S7 Edge. Since its unlocked firmware/OTA file I would assume it will be doable.
Normally you will have to keep the file in your sdCard and go to recovery mode and apply update from SD card but we will definitely have to do some testing if that doesn't work out.
Link for the OTA update bin file: https://mega.nz/#F!k6IjlJoC!VJJ3gyVaF8ofphE1fZvD8A
EDIT: found a way to download whole firmware will post sometime after midnight once I get off from work.
we cant flash .bin files. Doesnt work. We already tried.
thank you! I would love to know how to flash this if possible?
badboy47 said:
thank you! I would love to know how to flash this if possible?
Click to expand...
Click to collapse
1 possible way might be to extract the content of bin with 7zip. then compress it with 7zip as a zip file. name it the same name. put on sdcard and reboot to recovery. then apply update from sdcard and prey to what ever god you like that it works.
trying to help.
MrSteelX said:
1 possible way might be to extract the content of bin with 7zip. then compress it with 7zip as a zip file. name it the same name. put on sdcard and reboot to recovery. then apply update from sdcard and prey to what ever god you like that it works.
trying to help.
Click to expand...
Click to collapse
Nope is not working there are two errors 1st is e.footer is wrong and 2nd is signature verification failed
If someone has a Snapdragon S8 with bootloader unlocked and TWRP, maybe you can sideload it by disabling signature verification?
When flashing updates via stock recovery create a folder call FOTA in SD card and place file there rename it update.zip just make sure you don't end up with update.zip.zip
tlopez1973 said:
When flashing updates via stock recovery create a folder call FOTA in SD card and place file there rename it update.zip just make sure you don't end up with update.zip.zip
Click to expand...
Click to collapse
No, an error is displayed. Nothing is set.
55andrey55 said:
No, an error is displayed. Nothing is set.
Click to expand...
Click to collapse
what's the error you got?
MishaalRahman said:
If someone has a Snapdragon S8 with bootloader unlocked and TWRP, maybe you can sideload it by disabling signature verification?
Click to expand...
Click to collapse
Only snapdragons that have bootloader unlock is the Chinese edition and loading that would probably brick them or best casensrio perma lock their bootloader
Cameron581 said:
Only snapdragons that have bootloader unlock is the Chinese edition and loading that would probably brick them or best casensrio perma lock their bootloader
Click to expand...
Click to collapse
It wouldn't do either of those. It would just fail.
suyash1629 said:
what's the error you got?
Click to expand...
Click to collapse
Just went live in the US man through the Samsung plus app and I got in. Only 10k spots
Stevieboy02008 said:
Just went live in the US man through the Samsung plus app and I got in. Only 10k spots
Click to expand...
Click to collapse
Yup I saw it just went live. I reverted back to Nougat and was trying to get the OTA update.zip file. And noticed that it just went live. For some reason it did not detect that I was already registered and asked me to registered again. I wonder if everyone who did it by bypassing server has to register again to claim their actual spot for later updates.
suyash1629 said:
Yup I saw it just went live. I reverted back to Nougat and was trying to get the OTA update.zip file. And noticed that it just went live. For some reason it did not detect that I was already registered and asked me to registered again. I wonder if everyone who did it by bypassing server has to register again to claim their actual spot for later updates.
Click to expand...
Click to collapse
Don't know and don't care. It's downloading officially now brother and I'm a happy camper lol once it download I will do factory reset and have it fresh
Does anyone know if we can use SamPWND root method but without clearing cache? I am assuming I can do that by not flashing CSC which contains the cache partition.
I am trying to grab update.zip from cache partition.
Turns out my assumption of update.zip file being stored in /cache were wrong its actually stored in /data/fota folder. I guess we are out of luck here. I was thinking what is that converts .bin file to .zip file instantly after downloading onto Galaxy S8. I don't see any other way beside renaming and adding signature (though it already has the signature from Samsung.
suyash1629 said:
Turns out my assumption of update.zip file being stored in /cache were wrong its actually stored in /data/fota folder. I guess we are out of luck here. I was thinking what is that converts .bin file to .zip file instantly after downloading onto Galaxy S8. I don't see any other way beside renaming and adding signature (though it already has the signature from Samsung.
Click to expand...
Click to collapse
Well I have a question for you brother.
I just officially download and installed it. But wanted to do a fresh start basically a factory reset and download everything from scratch. If I do the factory reset would it kick me out of beta and take me back to 7.0 or just take me back to 7.0 or will start with 8.0?
Stevieboy02008 said:
Well I have a question for you brother.
I just officially download and installed it. But wanted to do a fresh start basically a factory reset and download everything from scratch. If I do the factory reset would it kick me out of beta and take me back to 7.0 or just take me back to 7.0 or will start with 8.0?
Click to expand...
Click to collapse
factory reset will stay on 8.0
Would it kick me out of the beta program though. That's the most important thing for me ?
---------- Post added at 08:34 PM ---------- Previous post was at 08:03 PM ----------
cam30era said:
factory reset will stay on 8.0
Click to expand...
Click to collapse
Please advice on my earlier question brother.
You guys think FlashFire could flash it?
I reverted to stock after messing up my BLN-L24. The ROM is a bit different than the one that shipped with the phone. Some apps are missing. The play store doesn't seem to detect updates even though they can be updated manually when searched. The phone also wont let me update to the latest version. The os it shipped with could update to the latest security update. The play store also says the phone is uncertified. Why is this ROM different? Is there any way i can force an update?
is model number and everything in about section still the same ?
sreekantt said:
is model number and everything in about section still the same ?
Click to expand...
Click to collapse
Yea. I figured it out. I flashed the updates in the wrong order. So i was missing all of the USA files because they were flashed before the actual ROM
sreekantt said:
is model number and everything in about section still the same ?
Click to expand...
Click to collapse
Nevermind. Its still messed up. I dont understand why im not getting any of the USA features installed. i believe its all stock. BLN-L24C567B342 is the build number. BLN-L24 is the model number.
BakedOnSomeSour said:
Nevermind. Its still messed up. I dont understand why im not getting any of the USA features installed. i believe its all stock. BLN-L24C567B342 is the build number. BLN-L24 is the model number.
Click to expand...
Click to collapse
Don't u have any old TWRP backup which consists of OEM info, vendor, product, boot ???
If not, i think you have to use Huawei update extractor on US firmware
Twrp backup would have made the process easy and reliable
There is something very screwed up with the OTA updates for this model phone right now. Consider yourself lucky that your phone still works, I'm dealing with a BLN-L24 that is more than likely unrecoverable all due to some wierd firmware that the official updater installed on the phone on Christmas Eve. Its like the servers are sending bad firmware that isn't for this model but the phone accepts it since it's OTA.
If you haven't read it yet please check out my thread and tell me if you are experiencing anything similar since your OTA. Check out the 3rd post too.
https://forum.xda-developers.com/honor-6x/help/bln-l24-stuck-device-booting-rollback-t3725319
I forgot to mention in my post that overall the phone ran extremely sluggish for a fresh update even though I have no idea what firmware was on the phone. All I know is it was completely foreign to me in all aspects....it was just very wierd overall and in pretty sure you know exactly what I mean since you said it was different.
As for uncertified in play store, try clearing app data for play store and see if it changes to certified.
sreekantt said:
Don't u have any old TWRP backup which consists of OEM info, vendor, product, boot ???
If not, i think you have to use Huawei update extractor on US firmware
Twrp backup would have made the process easy and reliable
Click to expand...
Click to collapse
Unfortunately i don't. I will try to flash the files from the update file with the extractor.
BakedOnSomeSour said:
Unfortunately i don't. I will try to flash the files from the update file with the extractor.
Click to expand...
Click to collapse
Yeah...try
Verify if u downloaded from the appropriate firmware
http://pro-teammt.ru/firmware-database/?firmware_model=BLN-L24C567&firmware_page=0
sreekantt said:
Yeah...try
Verify if u downloaded from the appropriate firmware
http://pro-teammt.ru/firmware-database/?firmware_model=BLN-L24C567&firmware_page=0
Click to expand...
Click to collapse
I flashed the vendor, boot, recovery, and system images with fastboot and then installed the update through erecovery. First i flashed update.zip. Then i flashed update_data_full_BLN-L24_hw_usa. Im still missing all of the USA features. I know all of the apks are in the update_data_full_BLN-L24_hw_usa folder but they arent being put on the system. Is there something i could be missing? Also the install time for update_data_full_BLN-L24_hw_usa is rather short for its size. Is it just being skipped?
BakedOnSomeSour said:
I flashed the vendor, boot, recovery, and system images with fastboot and then installed the update through erecovery. First i flashed update.zip. Then i flashed update_data_full_BLN-L24_hw_usa. Im still missing all of the USA features. I know all of the apks are in the update_data_full_BLN-L24_hw_usa folder but they arent being put on the system. Is there something i could be missing? Also the install time for update_data_full_BLN-L24_hw_usa is rather short for its size. Is it just being skipped?
Click to expand...
Click to collapse
Just to confirm we r on the same lines
U just mentioned that u flashed update.zip
Did u mean 'install it via dload method' .....If installing via dload method...u need to extract update.zip and place the contents in dload folder of sd card.
If u r doing the same....what are the exact apps and features which are missing ?
sreekantt said:
Just to confirm we r on the same lines
U just mentioned that u flashed update.zip
Did u mean 'install it via dload method' .....If installing via dload method...u need to extract update.zip and place the contents in dload folder of sd card.
If u r doing the same....what are the exact apps and features which are missing ?
Click to expand...
Click to collapse
Yes by flash i mean using the dload method. I extracted the content of the update.zip and put it in the dload folder on the sd card. After that i put the files from update_data_full_BLN-L24_hw_usa folder into dload and run the update. When the phone boots i am taken to a rather boring stock setup without any bloat apps. Its missing default wallpapers and themes. The play store fails to detect that the preinstalled apps need updates. Its almost like a completely different phone. A completely different broken phone. The apps below should be on the phone
UPDATe: Got an OTA and everything is back to normal. Thanks for the help
BakedOnSomeSour said:
Yes by flash i mean using the dload method. I extracted the content of the update.zip and put it in the dload folder on the sd card. After that i put the files from update_data_full_BLN-L24_hw_usa folder into dload and run the update. When the phone boots i am taken to a rather boring stock setup without any bloat apps. Its missing default wallpapers and themes. The play store fails to detect that the preinstalled apps need updates. Its almost like a completely different phone. A completely different broken phone. The apps below should be on the phone
UPDATe: Got an OTA and everything is back to normal. Thanks for the help
Click to expand...
Click to collapse
:highfive: nice
Hi,
I bought my phone three months back. Ever since the last update Version Name - WW18.0840.2106.86 my wifi and Hotspot just won't turn on.
I have been through the asus forum and seems like alot of customers are facing this issue.
One of them confirmed that even after replacing motherboard the issue persists. Others are facing air trigger issues after replacing the motherboard.
Just wanted to know if anyone here is facing similar issues.
DO let me know your thoughts on should I visit service center and Get my motherboard replaced or should I wait for the next update. My current Version Name - WW18.0840.2107.151
PS: My phone is not rooted
Thanks
I have not had these issues personally. I just updated to .151 last night though, so we shall see.
The general consensus is that the mobo needs to be replaced, and will most likely not get fixed with a software update. If it was correctable, a major issue like this would have forced a new FW update after .86 caused your initial problem.
You could always try flashing raw FW if you really want to tinker, but I doubt it will help. I would hit the service center and get the mobo replaced.
Good luck!
BILLYB187 said:
I have not had these issues personally. I just updated to .151 last night though, so we shall see.
The general consensus is that the mobo needs to be replaced, and will most likely not get fixed with a software update. If it was correctable, a major issue like this would have forced a new FW update after .86 caused your initial problem.
You could always try flashing raw FW if you really want to tinker, but I doubt it will help. I would hit the service center and get the mobo replaced.
Good luck!
Click to expand...
Click to collapse
Yup.. .86 update cause this. I just didn't want to change the motherboard,as it will change the imei of phone from what's on the box.
Thanks for your inputs though
I was helped by installing the karnel
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
thieftime1980 said:
I was helped by installing the karnel
Click to expand...
Click to collapse
Really? I have same problem after update. It didn't allow me to turn on wifi. But if its sure that installing kernel would solve the problem I might give it a try
Would you elaborate your situation regarding this sir?
jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
TOYOBHUMAX said:
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
Click to expand...
Click to collapse
The ota files are installed right in system.
New firmware "keep root" WW-18.0840.2103.26
Okay so I went to the Asus website https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method...
forum.xda-developers.com
twistedumbrella said:
The ota files are installed right in system.
New firmware "keep root" WW-18.0840.2103.26
Okay so I went to the Asus website https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method...
forum.xda-developers.com
Click to expand...
Click to collapse
Nothing pops up
thieftime1980 said:
I was helped by installing the karnel
Click to expand...
Click to collapse
What kernel did you install?
https://forum.xda-developers.com/t/kernel-30-09-2021-android-11-kirisakura-1-2-0-for-asus-rog-phone-5-aka-anakin.4333363 / strona-5 # post-85712193
jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
How did you reboot to slot b? In twrp?
TOYOBHUMAX said:
How did you reboot to slot b? In twrp?
Click to expand...
Click to collapse
There is option in twrp check in reboot section
TOYOBHUMAX said:
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
Click to expand...
Click to collapse
Twrp
TOYOBHUMAX said:
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
Click to expand...
Click to collapse
I use twrp for ota files
jaleel (jelly) said:
I use twrp for ota files
Click to expand...
Click to collapse
Hi thanks for the answer... How to install OTA files in twrp? You mean OTA files the one beginning with UL or WW
anybody found a real solution? i was fine and after i flashed a kernel later that day no wifi, I went bk to stock and no luck
chairman011 said:
anybody found a real solution? i was fine and after i flashed a kernel later that day no wifi, I went bk to stock and no luck
Click to expand...
Click to collapse
No one shares how lol. I guess theyre not here. Im struggling same problem too man
TOYOBHUMAX said:
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
Click to expand...
Click to collapse
OTA files are the standard updates. There are a lot of how to guides that answer most of these questions, which may be why nobody is jumping up to walk you through it.
I wouldn't trust someone installing OTA files in TWRP because the system handles them already without any software. That is just asking for problems.
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
The link I posted earlier is included in that. Not sure why nothing showed up for it, but maybe you'll have better luck getting to it that way.
There's always a possibility it is a hardware issue. A lot of them have been SIM, Wifi, and Bluetooth issues. If you suspect a kernel issue, make sure you are following the instructions to restore. If you only flashed a boot, you didn't follow the instructions.