Hi folks,
Looking for a little help here.
I have been following Omar-Avelar's rom and updating it as and when new versions are released, and prior to the conflict arising when Omar changed the kernal, I had been using Arman68's AIO. Today I perhaps foolishly updated to Omar's April 19th update along with Arman's AIO V5. This combination wouldn't boot...no big issue, just reinstall Omar's rom as a stand alone. However, this just gets in a perpetual bootloop off>fugly unlocked bootloader warning>motorola logo>intel logo>off ad infinitum.
I then tried to flash 91.2.26001 Orange Gb and 91.2.26001 EU...but they don't get past the little android guy in the flash process...he just falls over and the process quits.
I can access CWM Recovery just fine, but I don't seem to be able to flash a working rom from there.
Following this, I installed RSDLite, hoping to effect a fix from there...but because the phone is cycling, windows doesn't pick it up.
Any solutions, gratefully received
Coxie
Coxie said:
Hi folks,
Looking for a little help here.
I have been following Omar-Avelar's rom and updating it as and when new versions are released, and prior to the conflict arising when Omar changed the kernal, I had been using Arman68's AIO. Today I perhaps foolishly updated to Omar's April 19th update along with Arman's AIO V5. This combination wouldn't boot...no big issue, just reinstall Omar's rom as a stand alone. However, this just gets in a perpetual bootloop off>fugly unlocked bootloader warning>motorola logo>intel logo>off ad infinitum.
I then tried to flash 91.2.26001 Orange Gb and 91.2.26001 EU...but they don't get past the little android guy in the flash process...he just falls over and the process quits.
I can access CWM Recovery just fine, but I don't seem to be able to flash a working rom from there.
Following this, I installed RSDLite, hoping to effect a fix from there...but because the phone is cycling, windows doesn't pick it up.
Any solutions, gratefully received
Coxie
Click to expand...
Click to collapse
If you can enter fastboot mod, just download sbf form http:?/sbf.droid-developers.org/smi/list.php (sorry for the link...) and RSDlite 6.1.4,
Make sure you have drivers installed, enter to fastboot mod, wait untill phone is detected, choose your sbf and let RSD do his job.
Enter in the CWM and try to make a full wipe.
[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac
Q&A for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
lamhcmute said:
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
Click to expand...
Click to collapse
In post# 1 under the downloads section, below version 03 you will find revert longpress to recents & menu. You can download and flash this zip through recovery and menu key will be as before.
no root after flashign WizCyan
After flashing WizCyan 4 with update 1 I don't have root access. I've tried reinstalling several times and I've also tried to install superSU on it's own using CWM, both the latest version and older versions, with no success. I've also tried to install just v4 but the problem persists. Does anybody have any clue on what could be wrong? I've had root on the phone using other ROMs. I use the latest CWM.
And yes, I chose no when promted to fix superuser in CWM. Although I have also tried to pres yes during one installation.
What version of cwm are you having? Also when you click on the supersu app what message do you get?
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Gudiol said:
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Click to expand...
Click to collapse
I would suggest that you do a clean install of the ROM, now that your recovery has been updated
Excessive consumption of battery
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Will suggest to do a clean install and check and if not then report back. Anyone else facing this issue.. kindly report
srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Ok, did some testing and found that some of the init.d scripts were eating battery therefore have posted an update in the OP removing these and battery consumption should be better after flashing this update.
can i install
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
s4active user said:
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
Click to expand...
Click to collapse
Sure, you can install on any firmware, but if you have wifi issues then you may need to flash modem or some other workaround. Just wipe data/factory reset and install version 04 followed by update 02. I am not sure on what you mean by memory but presume that you are referring to internal sd card. This will depend on what apps/features you install from the addon package and playstore. The ROM will not affect your internal sdcard space as it will be installed on the reserved system space.
Problem with Rom Super Wizcyan - S5 Style
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Kaitenx said:
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Click to expand...
Click to collapse
In case you want to use screen mirroring then you would need to install allshare from the addon package
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Still can't get my Wifi to enable. The flash was successful, as I can see the correct baseband on the "about" screen, but it refuses to enable. I'm in Australia, but I believe this phone came from UAE -- would that make a difference to the way the modem interacts with the Wifi hardware? I pulled this info from logcat:
Code:
I/WifiManager( 1084): setWifiEnabled : true
I/WifiService( 882): setWifiEnabled: true pid=1084, uid=10008
E/WifiHW ( 882): ##################### set firmware type 0 #####################
E/WifiHW ( 882): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 882): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 882): return of insmod : ret = -1, Exec format error
E/WifiStateMachine( 882): Failed to load driver
E/WifiStateMachine( 882): sendErrorBroadcast code:10
E/WifiController( 882): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
In the mean time, I'm going to try to source either a local radio, or one from the original region, to see if that helps.
andycore said:
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Click to expand...
Click to collapse
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
JASONRR said:
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
Click to expand...
Click to collapse
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
andycore said:
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
Click to expand...
Click to collapse
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
JASONRR said:
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
Click to expand...
Click to collapse
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
andycore said:
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
Click to expand...
Click to collapse
Glad to know that you managed to get the wifi working.
Personally, I did not face the wifi issue after flashing PHN firmware, but know that quite a few have faced this issue as reported in this thread
Normally my understanding and experience is that when you flash different modems / firmware some corruption occurs and factory reset from within the phone resets the partition & firmware. 1st time I experienced this was when I was using a MTK 6575 based device and had amended the EBR, MBR and scatter files to modify the partition sizes, even though these were flashed through mobiuncle tools (similar to odin), the revised partitions did not get changed until I did a factory reset from within the phone. I know that this is irrelevant here but thought that I would share this.
Hello, I've never flashed phones before, so I might have just make some obvious mistake, that I'm not aware of.
After using my XPS 4.3 for over 2 years it started lagging, so I wanted to switch to some custom ROM.
First I wanted to try XperianZe v3.0.5 , but after 2 days of constant fails, anything will do.
First I wanted to root, but Towelroot doesn't work for me (I'm currently staying in China, so I suspect it might be the Great Firewall of China blocking it's connection attempts), but I found another way. I downloaded newest Flashtools (0.9.22.0) and ftf images from the post, but flashtools doesn't see them, so I downloaded an older version of Flashtools (0.9.18.6) and flashed the kernel which made my phone fall into a bootloop. I downloaded whole image C5303_12.0.A.2.254_CE.ftf of stock version 4.1, flashed C530X_12.0.A.1.257 kernel on top of it, and run DooMLoRD script, which gave me root access.
Now I installed CWM from here and copied XperianZeV3.zip to internal storage. I disconnected my phone, entered recovery, factory reseted and chose install from zip. It doesn't matter which recovery I used: CWM Touch/ TWRP/ Philz - all gave the same result:
Code:
set_metadata_recursive: some changes failed
E:Error in /data/media/XperianZeV3.zip
(Status 7)
Installation aborted.
This is latest version of CWM_SP_4.4.1 that I could find.
Unable to bypass this problem I decided to unlock bootloader and while doing so get MoKee Marshmallow 60.1 . But Sony website told me that my particular phone cannot be unlocked. I tried to unlock it anyway, but fastboot doesn't see my device when it eneters flash-boot (and automatically exits after some time). I couldn't install Flashtool drivers, because of some error with no message, it might be because of Windows 10, maybe? Anyway as I understand from this tutorial there's no unofficial way of unlocking my phone.
The only thing that I found about Status 7 problem is to update CWM (but I'm using latest one, aren't I?), tell the cellphone to ignore the problem (but I'm afraid of bricking it). I don't really understand what is this problem related to, other that name change between Kitkat and earlier systems, but I don't know how to make it work.
Am I just doing something wrong?
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.