I updated my firmware with Newflasher to 50.1.A.5.59, however now whenever I install Xposed, it bootloops. It was working fine on the previous firmware, however when I flash the older stock firmware, it bootloops also.
Upon running the command 'fastboot getvar all', it seems that the bootloader does indeed downgrade back down with the rest of the firmware package, while the command line in newflasher says success on the the baseband, it seems to have some kind of lock preventing a lower version from staying flashed, so now I'm stuck on the newer firmware.
Does anyone know any possible way to override this, and be able to successfully downgrade the baseband? I really want to get Xposed working again
EDIT: After failing with Newflasher, Sony has updated Emma flashtool I was able to successfully downgrade the baseband.
Edit 2: I got a discovery device that was on the 5.59 firmware and was able to downgrade with Androxyde Flashtool, however Newflasher would not work downgrading that device either.
Have you tried to flash systemless xposed module via MagiskManager?
bloodclot said:
Have you tried to flash systemless xposed module via MagiskManager?
Click to expand...
Click to collapse
Same soft brick result. It has to do with the March update that is causing Xposed not to work.
bloodclot said:
Have you tried to flash systemless xposed module via MagiskManager?
Click to expand...
Click to collapse
Yes... Since upgrading the firmware, I've tried installing it with Magisk, TWRP, and directly through the Xposed installer app, all 3 ways result in a bootloop since I upgraded to the newest firmware.
I tried to downgrade, but the baseband is stuck on the newer version. i.e. it won't downgrade with the rest of the firmware, so I'm assuming there's some kind of write protection that won't allow it to be downgraded. I'm wondering if anyone knows how to get around it and force it to take the lower version of the baseband. The bootloader version downgrades without any issue, but it won't boot up with a mismatching baseband.
li0nh3art3d said:
Yes... Since upgrading the firmware, I've tried installing it with Magisk, TWRP, and directly through the Xposed installer app, all 3 ways result in a bootloop since I upgraded to the newest firmware.
I tried to downgrade, but the baseband is stuck on the newer version. i.e. it won't downgrade with the rest of the firmware, so I'm assuming there's some kind of write protection that won't allow it to be downgraded. I'm wondering if anyone knows how to get around it and force it to take the lower version of the baseband. The bootloader version downgrades without any issue, but it won't boot up with a mismatching baseband.
Click to expand...
Click to collapse
Since this is my first Sony phone, I don't know if the same applies but I would guess that S-OFF is needed to fully downgrade the firmware, and who knows if anyone ever figures out a way to S-OFF it.
li0nh3art3d said:
[...] now whenever I install Xposed, it bootloops [...](
Click to expand...
Click to collapse
- Go into recovery and create a backup of the /system partition (if something goes wrong in the next step, just restore it)
- Download and flash rovo's official xposed zip beta2 - stay away from beta3 for now!!
- You must be done!
Xposed beta2 is working great here on my Xperia X Performance - April Security Patch
Edit... got bootloop after installation of a testing xposed module. I'll check it out
Edit 2... testing module was the culprit!
Edit 3... installing modules that hook in system apps leads in bootloop (gravitybox, xprivacylua, xperia home x, ...) - Useless!
serajr said:
- Go into recovery and create a backup of the /system partition (if something goes wrong in the next step, just restore it)
- Download and flash rovo's official xposed zip beta2 - stay away from beta3 for now!!
- You must be done!
Xposed beta2 is working great here on my Xperia X Performance - April Security Patch
Edit... got bootloop after installation of a testing xposed module. I'll check it out
Edit 2... testing module was the culprit!
Edit 3... installing modules that hook in system apps leads in bootloop (gravitybox, xprivacylua, xperia home x, ...) - Useless!
Click to expand...
Click to collapse
I was actually using GravityBox and Xperia Home on 50.1.A.4.102 (first update; phone ships on 50.1.A.76), it's when I updated to 50.1.A.5.59 and flashed xposed framework again, it wouldn't boot.
serajr said:
Edit 3... installing modules that hook in system apps leads in bootloop (gravitybox, xprivacylua, xperia home x, ...) - Useless!
Click to expand...
Click to collapse
That's because the March and April security updates have made Xposed useless due to how the system hooks work. Until a work around is found we are Xposed less right now.
AngryManMLS said:
That's because the March and April security updates have made Xposed useless due to how the system hooks work. Until a work around is found we are Xposed less right now.
Click to expand...
Click to collapse
according to this there is a workaround, made by @serajr, that can be done by deodexing (or de-vdexing since oreo is vdex?) the system/framework/services.jar file and then editing it, but I can't figure out how to deodex/de-vdex... But the good news is that the fix is reported to be working for the XZP, and if done correctly should also work on the XA2 also.
tbh, it would be nice to completely deodex or de-vdex the entire rom.
li0nh3art3d said:
according to there is a workaround, made by @serajr, that can be done by deodexing (or de-vdexing since oreo is vdex?) the system/framework/services.jar file and then editing it, but I can't figure out how to deodex/de-vdex... But the good news is that the fix is reported to be working for the XZP, and if done correctly should also work on the XA2 also.
tbh, it would be nice to completely deodex or de-vdex the entire rom.
Click to expand...
Click to collapse
FWIW, [URL="https://forum.xda-developers.com/showthread.php?t=1755243"]APKTool is what I had used 4-5 years ago on the Samsung Galaxy S3 to get the framework and system/services.jar files, and possibly one or two other files. I had merely done that so I could integrate the 3MinitBattery mod into the stock and stock-based 4.4.x ROMs. I haven't successfully touched it since then, though. I think I tried using it on the VS985 Verizon LG G3 stock ROM without any luck, but that's been awhile.
There is an official for the tool as well at https://ibotpeaches.github.io/Apktool/ by the author, as well.
I got it deodexed, and patched the services.jar, but it still bootlooped. It seems like the march security patch messed up Xposed for almost all oreo devices. Some can't run certain modules, while others won't even boot.
I really miss GravityBox
Has anyone had success downgrading the baseband from the 50.1.A.5.59 update? I can't be the only one that's tried...
Anyone had luck with this? Really miss using xposed.
baj24 said:
Anyone had luck with this? Really miss using xposed.
Click to expand...
Click to collapse
I was able to downgrade the baseband. I simply flashed back to 4.76. Xposed and Gravitybox works normal. Now will upgrade to 4.102 and stay there.
Konomastiker said:
I was able to downgrade the baseband. I simply flashed back to 4.76. Xposed and Gravitybox works normal. Now will upgrade to 4.102 and stay there.
Click to expand...
Click to collapse
where did you download the firmware from? Xperifirm only has the latest...
li0nh3art3d said:
where did you download the firmware from? Xperifirm only has the latest...
Click to expand...
Click to collapse
I installed Sony flash utility EMMA, it found 4.76 and 5.59. You also can download it from Android File Host. Just searched for my model H3213
Konomastiker said:
I installed Sony flash utility EMMA, it found 4.76 and 5.59. You also can download it from Android File Host. Just searched for my model H3213
Click to expand...
Click to collapse
I have the H3123, but I registered for emma and verified my email address but it says my account won't be active until I contact a representative for sony mobile. I'm not sure how to do that... It doesn't give me any sort of link or address to email.
EDIT: So I found the firmware on Android file host, however I'm just waiting for my Emma account to be activated ?
li0nh3art3d said:
I have the H3123, but I registered for emma and verified my email address but it says my account won't be active until I contact a representative for sony mobile. I'm not sure how to do that... It doesn't give me any sort of link or address to email.
EDIT: So I found the firmware on Android file host, however I'm just waiting for my Emma account to be activated
Click to expand...
Click to collapse
I did not mess with email and activation. For me, emma was free downloadable. Go to https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/ and download it. Maybe it depends on where you are at.
PS: Just looked closer to the page. Emma was deactivated on 6 July 2017. I used it before this date. But you still can download it from Germany. You will have to try if you can install it and if it will work.
li0nh3art3d said:
EDIT: So I found the firmware on Android file host, however I'm just waiting for my Emma account to be activated ?
Click to expand...
Click to collapse
Is the one you grabbed H3223_Customized US_1312-1380_50.1.A.4.102_R6A.rar by any chance?
AngryManMLS said:
Is the one you grabbed H3223_Customized US_1312-1380_50.1.A.4.102_R6A.rar by any chance?
Click to expand...
Click to collapse
H3123
I'm disappointed in Sony. What should have been a simple account activation is now turning into runaround.
this is bs. This paula C doesn't understand the difference between a developer and a technician nor what an unlocked bootloader is ?
Related
Has anyone attempted to install xposed on the honor 8?
Yes, works. Arm64.
I can confirm, XPosed can be installed...
Albeit it seems to have a "small" bug - for me the dialer did stop working when xposed was installed (could not make any call)
V86 ARM64 xposed by rovio...
will need to investigate further.
Can anyone confirm/deny/did find a workaround?
I have xposed and dialer is working fine. Maybe it's some particular mod you've installed.
I tried installing xposed from this link http://dl-xda.xposed.info/framework/sdk23/arm64/ but I'm always getting a bootloop. Did you use another zip file?
ppalfinger said:
I tried installing xposed from this link http://dl-xda.xposed.info/framework/sdk23/arm64/ but I'm always getting a bootloop. Did you use another zip file?
Click to expand...
Click to collapse
For me, xposed did work using magisk + systemless xposed (material xposed intaller + v86.5); as well as using v86 - i think the version you posted.
I could revert my previous dialer problem by rebooting several times till all files have been treated by xposed as they should have been...
DThought said:
I can confirm, XPosed can be installed...
Albeit it seems to have a "small" bug - for me the dialer did stop working when xposed was installed (could not make any call)
V86 ARM64 xposed by rovio...
will need to investigate further.
Can anyone confirm/deny/did find a workaround?
Click to expand...
Click to collapse
I confirm the 'Dialer' bug you're facing. I have faced the same bug on all of the Honor devices I have owned. Whenever I hit the 'Call' button, the app crashes. A simple reboot does fixes the problem but it soon re-appears. No fix for it though.
DThought said:
For me, xposed did work using magisk + systemless xposed (material xposed intaller + v86.5); as well as using v86 - i think the version you posted.
I could revert my previous dialer problem by rebooting several times till all files have been treated by xposed as they should have been...
Click to expand...
Click to collapse
so how did you do this? i only read quick on the magisk thread but it said to flash magisk on a unrooted newly wiped phone.
is this true or can i flash it on my newly rooted honor 8?
hackslash said:
I confirm the 'Dialer' bug you're facing. I have faced the same bug on all of the Honor devices I have owned. Whenever I hit the 'Call' button, the app crashes. A simple reboot does fixes the problem but it soon re-appears. No fix for it though.
Click to expand...
Click to collapse
is it still possible to accept calls when the dialer is bugged and crashes?
also, which xposed version did you use?
JimZiii said:
so how did you do this? i only read quick on the magisk thread but it said to flash magisk on a unrooted newly wiped phone.
is this true or can i flash it on my newly rooted honor 8?
is it still possible to accept calls when the dialer is bugged and crashes?
also, which xposed version did you use?
Click to expand...
Click to collapse
About magisk,
you have to unroot your device from SuperSU. After that flash the stock boot image if available (unrooting from SuperSU usually suffices but if it doesn't works, it better to flash stock boot image)
About Xposed dialer bug (on EMUI only), yes as far as I know, I never experienced any crashes while accepting calls.
hackslash said:
About magisk,
you have to unroot your device from SuperSU. After that flash the stock boot image if available (unrooting from SuperSU usually suffices but if it doesn't works, it better to flash stock boot image)
About Xposed dialer bug (on EMUI only), yes as far as I know, I never experienced any crashes while accepting calls.
Click to expand...
Click to collapse
i feel extremely stupid here. i'm reading on the magisk thread and i don't understand at all.
i got a honor 8 (FRD-L09) and i've rooted it, like i mentioned earlier.
can you please help me with the steps i need to take to unroot and whatever else i need to do to flash magisk?
i can't find stock rom for my FRD-L09, so what do you suggest? just doing a full factory reset, flashing twrp, flashing magisk, rooting, restoring to the backup i create before doing the factory reset.
what do you think about those steps and in that order? if you think i need to change something or add another step please let me know.
not sure if that's enough to unroot the device, i'm also really uncertain about the correct magisk version/file i need to flash for my device. other xposed versions have different files for arm, arm64 and x86, but here there's only one file. am i missing something or does this work on all versions? or have i misunderstood how it works?
sorry about throwing so many questions at you but i'm really confused about this.
JimZiii said:
i feel extremely stupid here. i'm reading on the magisk thread and i don't understand at all.
i got a honor 8 (FRD-L09) and i've rooted it, like i mentioned earlier.
can you please help me with the steps i need to take to unroot and whatever else i need to do to flash magisk?
i can't find stock rom for my FRD-L09, so what do you suggest? just doing a full factory reset, flashing twrp, flashing magisk, rooting, restoring to the backup i create before doing the factory reset.
what do you think about those steps and in that order? if you think i need to change something or add another step please let me know.
not sure if that's enough to unroot the device, i'm also really uncertain about the correct magisk version/file i need to flash for my device. other xposed versions have different files for arm, arm64 and x86, but here there's only one file. am i missing something or does this work on all versions? or have i misunderstood how it works?
sorry about throwing so many questions at you but i'm really confused about this.
Click to expand...
Click to collapse
Take a complete backup just in case.
Perform a full unroot via SuperSU (find it in Settings). It will restore the modded files with the original ones hence reverting your boot image to the stock one.
Perform a full Factory reset. (remember to backup crucial data before attempting it)
Download B101 FRD-L09 stock ROM from here: http://loadbalancing.modaco.com/download.php?file=dload-honor-8-frdl09-frd-b101.zip
Extract the downloaded zip. There will be two folders, 'Part 1' and Part 2'. On your external SD card, create a folder 'dload'. Copy 'Update.APP' from 'Part 1' to the dload folder in your SD card. Power down the device. Hold Power Button + Volume Up + Volume Down buttons until you see the Honor logo. Your device will now automatically start installing the complete stock ROM. If in case your device boots to TWRP, then follow the below steps:
Download Huawei Update Extractor from here: http://forum.xda-developers.com/showthread.php?t=2433454
Use Huawei Update Extractor to extract RECOVERY from the Update.APP inside 'Part 1'.
Use 'fastboot' to flash the stock recovery.
Now try installing the Update.APP. This time it will work. Repeat the steps for Update.APP inside 'Part 2'
You're now on fresh stock ROM.
Download magisk from http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get and flash it via TWRP.
hackslash said:
Take a complete backup just in case.
Perform a full unroot via SuperSU (find it in Settings). It will restore the modded files with the original ones hence reverting your boot image to the stock one.
Perform a full Factory reset. (remember to backup crucial data before attempting it)
Download B101 FRD-L09 stock ROM from here: http://loadbalancing.modaco.com/download.php?file=dload-honor-8-frdl09-frd-b101.zip
Extract the downloaded zip. There will be two folders, 'Part 1' and Part 2'. On your external SD card, create a folder 'dload'. Copy 'Update.APP' from 'Part 1' to the dload folder in your SD card. Power down the device. Hold Power Button + Volume Up + Volume Down buttons until you see the Honor logo. Your device will now automatically start installing the complete stock ROM. If in case your device boots to TWRP, then follow the below steps:
Download Huawei Update Extractor from here: http://forum.xda-developers.com/showthread.php?t=2433454
Use Huawei Update Extractor to extract RECOVERY from the Update.APP inside 'Part 1'.
Use 'fastboot' to flash the stock recovery.
Now try installing the Update.APP. This time it will work. Repeat the steps for Update.APP inside 'Part 2'
You're now on fresh stock ROM.
Download magisk from http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get and flash it via TWRP.
Click to expand...
Click to collapse
thnx. i followed your steps, with a few added ones. i didn't realize that my bootloader would lock up again after flashing stock so i had to unlock it and reflash twrp.
i did wonder about the root since all phones have different root versions and he's offering a one for all version, but i flashed it and i now got working root.
still not done tho, still got to install the magisk manager and xposed
but thank you so much for you help, really felt like i was fumbling in the dark there for a moment before asking you lol
EDIT:
that it let's you turn the root on and off with a switch is ingenious. but what does it mean that google pay is not working while root is on?
JimZiii said:
that it let's you turn the root on and off with a switch is ingenious. but what does it mean that google pay is not working while root is on?
Click to expand...
Click to collapse
Yes, while the root is on, all applications that include the 'SafetyNet' check will refuse to work (such as Android Pay, Pokemon Go). When you switch it off, everything will start to work again.
hackslash said:
Yes, while the root is on, all applications that include the 'SafetyNet' check will refuse to work (such as Android Pay, Pokemon Go). When you switch it off, everything will start to work again.
Click to expand...
Click to collapse
yea that was just me remembering it wrong, thought it said google pay instead of android pay, so when i googled it i didn't really find anything which made me wonder what this mysterious google pay app was lol
but now i googled the correct name and found it right away.
but yea, thnx a lot for you help and time
Does anyone have issues playing videos with magisk installed, and I mean the flashable magisk not just the magisk manager app
Hello
I'm looking for a module which permit to center clock in statut bar .
Someone can help me please ?
Someone has tested Gravity Box ?
Works fine ?
Some features of GravityBox are working, some not.
Changes in statusbar are not working.
Nas42O said:
Hello
I'm looking for a module which permit to center clock in statut bar .
Someone can help me please ?
Click to expand...
Click to collapse
Not a perfect solution but try Flat Style Indicators.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Nas42O said:
Someone has tested Gravity Box ?
Works fine ?
Click to expand...
Click to collapse
There is a rule to check if modules will work flawlessly on your device or not. It's simple. All modules that were designed keeping AOSP in mind will not work. EMUI is a completely different iteration if Android and hence many of the options in Gravity Box will not work on EMUI.
hackslash said:
Not a perfect solution but try Flat Style Indicators.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
There is a rule to check if modules will work flawlessly on your device or not. It's simple. All modules that were designed keeping AOSP in mind will not work. EMUI is a completely different iteration if Android and hence many of the options in Gravity Box will not work on EMUI.
Click to expand...
Click to collapse
Thanks for your answer..
I already tested flat style bar but i got some issues .. :/
Gravity box has many customisations, but if almost all not working.. :s
Im using the dual sim model e6633
I have the stock fm and kernel and bootlocker unlocked.
Under image enhancement ,there is no change ie.Vivid mode and no enhNcemnt are showing same effect
Can anyone help to solve this problem
Cheers
Not sure to understant, but have you flashed a kernel with DRM fix ?
When you unlock your bootloader you loose, photo quality, image enhancement...
I havent flashed any kernel yet.
I have the stock fm and kernel.
Plz help me how to get back the image quality :/
Noobie question :/
Sorry for bad english ?
Should i flash a kernel with drm fix??
flash kernel with DRM fix and you will have image preview
L33Tgod said:
flash kernel with DRM fix and you will have image preview
Click to expand...
Click to collapse
Can you suggest me the best kernel available with drm fix for e6633 dual.(in terms of image quality and battery life)
Im extremly sorry for asking such silly question.
dulquer said:
Can you suggest me the best kernel available with drm fix for e6633 dual.(in terms of image quality and battery life)
Im extremly sorry for asking such silly question.
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-z5/general/patched-stock-kernel-32-2-5-11-e6683-t3516979
this one is for E6683, i have no idea will it work on E6633
I will send you other one if i found
L33Tgod said:
https://forum.xda-developers.com/xperia-z5/general/patched-stock-kernel-32-2-5-11-e6683-t3516979
this one is for E6683, i have no idea will it work on E6633
I will send you other one if i found
Click to expand...
Click to collapse
I dont think so it will work.
Will zacharias.maladroit kernel work?
It have drm fix??
Thanks in advance
yes it will work, also this one should work because it is same phone
I have one more issue.
Finger print hardware not available?
Is this also because of unlocked bootloader??
dulquer said:
I have one more issue.
Finger print hardware not available?
Is this also because of unlocked bootloader??
Click to expand...
Click to collapse
Nope, that's because you have the US version of the Z5 dual and it has been specifically disabled. If you want to get the fingerprint sensor working you need to flash international firmware, or there are some threads that tell you what files you need to replace. Search and you should find what you're looking for.
Devo7v said:
Nope, that's because you have the US version of the Z5 dual and it has been specifically disabled. If you want to get the fingerprint sensor working you need to flash international firmware, or there are some threads that tell you what files you need to replace. Search and you should find what you're looking for.
Click to expand...
Click to collapse
When i reboot it works fine.But it comes once in a while.Also i have the stock fm (Middle East).
dulquer said:
When i reboot it works fine.But it comes once in a while.Also i have the stock fm (Middle East).
Click to expand...
Click to collapse
Then you should be fine. It might not be working occasionally because there might be a bug in the firmware you're using. My only suggestion would be to make sure you're on the latest version of the firmware for your region, or try flashing firmware from another region. I'm using Customized UK firmware and I have no issues with the fingerprint sensor. Short of that the only other option would be a hardware failure, but it sounds more like a software bug.
Devo7v said:
Then you should be fine. It might not be working occasionally because there might be a bug in the firmware you're using. My only suggestion would be to make sure you're on the latest version of the firmware for your region, or try flashing firmware from another region. I'm using Customized UK firmware and I have no issues with the fingerprint sensor. Short of that the only other option would be a hardware failure, but it sounds more like a software bug.
Click to expand...
Click to collapse
I will try flashing another firmware.Its showing new sofware available in support?.But not showing when opening it under softwate updates.
dulquer said:
I will try flashing another firmware.Its showing new sofware available in support?.But not showing when opening it under softwate updates.
Click to expand...
Click to collapse
Can you post a screenshot of your About Phone screen so I can see your build number?
Devo7v said:
Can you post a screenshot of your About Phone screen so I can see your build number?
Click to expand...
Click to collapse
Attached.
dulquer said:
Attached.
Click to expand...
Click to collapse
It looks like you're a couple firmware versions behind; the latest firmware released for your phone is 32.2.A.5.11. Since you mentioned that your phone won't automatically update itself through the software update it sounds like you may have modified your phone in such a way (i.e., unlocking the bootloader, or modifying system files) that you might have to manually flash the firmware to your phone. There is a program called Flashtool that you can use to download and flash firmware to your phone. It's a great tool and something that you can learn to use after a few minutes of reading in the support thread.
If you've made any modifications to your phone, it would be helpful to know what those are understand why your phone won't update on its own. But most likely you'll have to use Flashtool to update your phone.
EDIT: In the future if you want to see what the latest version of firmware is for your phone you can use the XperiCheck website.
Devo7v said:
It looks like you're a couple firmware versions behind; the latest firmware released for your phone is 32.2.A.5.11. Since you mentioned that your phone won't automatically update itself through the software update it sounds like you may have modified your phone in such a way (i.e., unlocking the bootloader, or modifying system files) that you might have to manually flash the firmware to your phone. There is a program called Flashtool that you can use to download and flash firmware to your phone. It's a great tool and something that you can learn to use after a few minutes of reading in the support thread.
If you've made any modifications to your phone, it would be helpful to know what those are understand why your phone won't update on its own. But most likely you'll have to use Flashtool to update your phone.
EDIT: In the future if you want to see what the latest version of firmware is for your phone you can use the XperiCheck website.
Click to expand...
Click to collapse
Thanks a lot mate.
I will update through flastoool(I have used before)
Cheers
Devo7v said:
It looks like you're a couple firmware versions behind; the latest firmware released for your phone is 32.2.A.5.11. Since you mentioned that your phone won't automatically update itself through the software update it sounds like you may have modified your phone in such a way (i.e., unlocking the bootloader, or modifying system files) that you might have to manually flash the firmware to your phone. There is a program called Flashtool that you can use to download and flash firmware to your phone. It's a great tool and something that you can learn to use after a few minutes of reading in the support thread.
If you've made any modifications to your phone, it would be helpful to know what those are understand why your phone won't update on its own. But most likely you'll have to use Flashtool to update your phone.
EDIT: In the future if you want to see what the latest version of firmware is for your phone you can use the XperiCheck website.
Click to expand...
Click to collapse
I have updated to the latest fm as you said(about phone attached)
I have also flashed zacharias kernel.
Problem is going worse.
My down speaker is not working :/ also image enhancement preview remains same (no Change).
Please help
Cheers
dulquer said:
I have updated to the latest fm as you said(about phone attached)
I have also flashed zacharias kernel.
Problem is going worse.
My down speaker is not working :/ also image enhancement preview remains same (no Change).
Please help
Cheers
Click to expand...
Click to collapse
Did you write all your data when you flashed the new firmware with Flashtool? Maybe try flashing again, but make sure you wipe everything so you're starting with a clean phone. Set up the phone and make sure everything works, then flash a custom kernel.
Devo7v said:
Did you write all your data when you flashed the new firmware with Flashtool? Maybe try flashing again, but make sure you wipe everything so you're starting with a clean phone. Set up the phone and make sure everything works, then flash a custom kernel.
Click to expand...
Click to collapse
I did the same thing as you have said and no Change :/
I've taken note of the severely limited amount of organized information available for the Verizon variant of the core prime, (see the amalgamation of posts in the main sm-g360v post...) and I'll attempt to provide what information I do have. Currently no recoveries or custom roms have been made publicly available, to my knowledge. This is a Verizon device after all, don't hold much hope towards unlocking the bootloader of this one. Root on latest firmware, setup for xposed framework, and viper4android setup detailed below in respective order.
Root on latest firmware
*Skip to step 7 if already rooted with supersu, data partition not overwritten to my knowledge, proceed with cation
Backup all data before proceeding. Acknowledge these steps will delete all content of your device. Proceeding with the following steps gives the implied understanding I am not responsible for any data on your device. You are responsible for your own data.
1. Setup Odin and d/l the lollipop stock rom here
2. Backup your data then extract the tar.md5 from the rar archive from above then flash it with odin
3. Setup your accounts with the setup wizard when finished if you'd like, then grab the latest version of kingroot. Either android or pc versions work. May need to attempt multiple times.
4. Once rooted with latest kingroot, (5.0.3 at the time of writing) open kingroot, open the main settings from the menu on the top right, press 'Uninstall Kingroot' press continue, ensure 'leave root backup' is enabled in the next dialog, then wait for uninstall
5. Find a kingroot 4.5 apk and install, disable automatic updates in kingroot main settings, then reroot
6. Using either super sume, or a script replace kinguser with supersu
7. Install flashfire, should work properly if using supersu
8. Go here and d/l latest firmware, move tar.md5 file to device, may need external sd due to little internal storage
9. In flashfire, press the addition symbol, select 'flash firmware package,' locate updated tar.md5, select 'modem firmware' and 'Firmware' in addition to pre-selected partitions, then select the check, when prompted, do not split flashing process. Ensure EverRoot is set to inject SuperSU, then flash, wait patiently for device to update.
When finished, check SuperSU for root, if prompted to manually install, flash first stock and try again
Xposed Framework
1. Get the appropriate zip (ARM for sm-g360v, do not use the ARM64) from here, no issues apparent between versions, latest will most likely work (87.1 at the time of writing, no issues seem thus far)
2. Flash as zip with Flashfire, (See above for root) do not mount /system with flashfire, installer fails.
3. Install this Xposed Framework app when reboot finished (should rebuild system apps)
4. Finished
Viper4Android
1. Get V4A apk, do not install drivers yet
2. Install busybox
3. Get this and this, flash both with flashfire
4. Disable/delete SoudAlive to prevent conflicts
5. Install driver/reboot
6. Finished *I personally installed the 2.5 version, though the above method did work with a little bit of toying with the above
I'm assuming that the Odin tar file is an older firmware version for the device?
Jrhotrod said:
I'm assuming that the Odin tar file is an older firmware version for the device?
Click to expand...
Click to collapse
The first tar is lollipop with a security patch from 2015 for kingroot, the second tar that gets flashed through flashfire can be any of the three available, I believe the 2017 build being latest
WARNING:
DO NOT, I repeat DO NOT flash the updated tar.md5!! I flashed it to my device and I lost all calling and texting functionality, PLUS a very outdated ROM.
Jrhotrod said:
WARNING:
DO NOT, I repeat DO NOT flash the updated tar.md5!! I flashed it to my device and I lost all calling and texting functionality, PLUS a very outdated ROM.
Click to expand...
Click to collapse
Use the latest build, the 2017 build is latest, update your modem partitions when you update. Following the steps PROPERLY and using the proper update package will result in a functional device. Complain to Verizon about the outdated nature of the firmware available, and to yourself about your own mistakes, I have used this procedure for my own device and have not had a single issue.
LeafyDeerVoid said:
Use the latest build, the 2017 build is latest, update your modem partitions when you update. Following the steps PROPERLY and using the proper update package will result in a functional device. Complain to Verizon about the outdated nature of the firmware available, and to yourself about your own mistakes, I have used this procedure for my own device and have not had a single issue.
Click to expand...
Click to collapse
I used the 30.10.2016 firmware (G360VVRU3CPJ1) and that's what gave me the issues. Now that I actually observe, I can see a 2017 firmware that I was actually using before I went back and rooted... I will test it soon.
How long should the final update take? I'm up to 30 mins now on the red Verizon screen (blue light strobing).
Chadtheguru said:
How long should the final update take? I'm up to 30 mins now on the red Verizon screen (blue light strobing).
Click to expand...
Click to collapse
Final update meaning what? An update package flashed via FlashFire? Or something else?
Step 9 in the op root process. I did everything up to that point, downloaded latest update, followed the flashfire steps and got 2 hours of the red Verizon screen. Any ideas?
I'm starting over. I screwed up something else anyhow trying to utilize the sd card for apps.
Okay, I started over from the beginning. I just can't get Flashfire to flash the updated firmware. It sticks on the red "Verizon" screen. I've let it sit for 3 hours and it is genuinely stuck. Help!
Chadtheguru said:
I'm starting over. I screwed up something else anyhow trying to utilize the sd card for apps.
Click to expand...
Click to collapse
I never attempted to update my software. Too risky. Stick with the G360VVRU3BOK2 baseband, there is virtually no difference between that and the new 2017 firmware.
Yeah, I've about come to the same conclusion. The only thing I don't like is the nagging OTA Update Notification. I've tried all these and I'm still getting the notify.
http://www.droidviews.com/disable-ota-notifications-android-devices/
Chadtheguru said:
Yeah, I've about come to the same conclusion. The only thing I don't like is the nagging OTA Update Notification. I've tried all these and I'm still getting the notify.
http://www.droidviews.com/disable-ota-notifications-android-devices/
Click to expand...
Click to collapse
Download the device control app from the Play Store and disable the Verizon "Software updates" app
Hah! That did it. Thanks!
Chadtheguru said:
Hah! That did it. Thanks!
Click to expand...
Click to collapse
Thanks for leaving a thanks :good:
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Jrhotrod said:
Thanks for leaving a thanks :good:
Click to expand...
Click to collapse
For future reference, OTAs are stored in /cache. If you feel like re-enabling the update app, you can let the update download and see if you can flash it with FlashFire. Never tried it myself, but FlashFire does come with an OTA update flasher that attempts to sustain root.
I almost tried that but I couldn't catch it with the OTA downloaded. I may fiddle with it later. Just glad to be rooted for now. Thanks again!
So I've done everything right, and all I've been wanting to install is Xposed. But I've done everything correct up to this point. But I put the framework zip into Flashfire, everything goes fine, until I'm at the Verizon red screen. It just hangs there for hours. Any suggestions?
Sent from my SM-G360V using Tapatalk
iiBootMii said:
So I've done everything right, and all I've been wanting to install is Xposed. But I've done everything correct up to this point. But I put the framework zip into Flashfire, everything goes fine, until I'm at the Verizon red screen. It just hangs there for hours. Any suggestions?
Click to expand...
Click to collapse
Better make sure you have the custom Wanam build.
Download link: https://www.androidfilehost.com/?w=files&flid=37508
Jrhotrod said:
Better make sure you have the custom Wanam build.
Download link: https://www.androidfilehost.com/?w=files&flid=37508
Click to expand...
Click to collapse
I'm pretty sure I'm using the right one. I followed the link, then went 87.1 > Lollipop > xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip
Isn't that correct?
Sent from my SM-G360V using Tapatalk
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Wait for the beta's
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Hi,
from what I have read, no, its not a daily driver, yet. I'd wait till the beta's are available in`May, to give it a try.
Though you could always just flash the update & see if it is OK for you. If not revert back to 10.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Not rootable yet. Lots of changes to it that Mr. Wu is going to have to work on. He said he knows what to do, just going to take a bit of time.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
I am on it and it is definitely stable enough to use as a DD but unfortunately no root yet
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
atembleque said:
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
Click to expand...
Click to collapse
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
wangdaning said:
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
Click to expand...
Click to collapse
Thanks!
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Vanschtezla said:
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Click to expand...
Click to collapse
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
sliding_billy said:
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
Click to expand...
Click to collapse
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Vanschtezla said:
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Click to expand...
Click to collapse
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
sliding_billy said:
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
Click to expand...
Click to collapse
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Vanschtezla said:
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Click to expand...
Click to collapse
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Vanschtezla said:
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Click to expand...
Click to collapse
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
Click to expand...
Click to collapse
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
Click to expand...
Click to collapse
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Vanschtezla said:
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Click to expand...
Click to collapse
I do not use that module, but it definitely sounds like it could be an issue since you weren't actually boot looped and were able to remove it. I try to keep my module use minimal (and use well vetted ones only) to avoid wondering whether they are the root cause of issues when they happen. Best of luck. Just glad you are up and running.
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you on Android 11 and have root?
Zehlek said:
Are you on Android 11 and have root?
Click to expand...
Click to collapse
No, this was OT from the original thread title when the question was asked about 10.
sliding_billy said:
No, this was OT from the original thread title when the question was asked about 10.
Click to expand...
Click to collapse
Sorry to stay OT, but since you mentioned EX kernel, does using it also not hide the unlocked bootloader in our "new and improved" SafetyNet world? I'm one of those for whom everything is still working so far--Pay, banking apps, device is certified, etc. I'd hate to lose all that, though, because I'm not going to unroot. I guess if I have to I can use Pay on my watch and use the banks' Web sites instead of their apps.
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.