[ME176CX]: Confused by alternatives... - MeMO Pad 7 Q&A, Help & Troubleshooting

Hi,
my ASUS ME176CX currently is:
* rooted
* xposed
* able to boot "anything" (unsigned bootloader)
* using L-Speed
and is running UL-K013-WW-12.10.1.24
So fine so nice...but:
My charging rate drops from 0.5% each minute to 0.125% each minute.
APK-files I download from apkpure reaches the external SD-card as *.zip files, which
I first have to rename to install them (so the structure as such is not touched).
May be all this problems are a result of my experimenting...
I think it is time for the total reset of everything.
But what to take?
* UL-K013-WW-12.10.1.24 again ?
* UL-K013-WW-12.10.1.33 (I read about a sever impact to battery life, though) ?
* UL-K013-WW-12.10.1.36 ?
* the russian lite version of the 36er firmware (I read of not working audio/gps/camera with this?)
* anything else which I had not found while searching?
And: Since TWRP now is installed, I would flash whatever it is advisable to flash with that...
and overwriting the code of a running program -- in this case the flashing application: TWRP itsself.
At this point I need the help of some deep gurus, I think?
How should I flash what firmware to get "the most" (less lagging, more battery life) out of my tablet?
Thank you very much for any help!
Cheers,
Noriatell
PS: Does anyone has experienced any wearout of the internal flash due to write cycles so far?

i use .36 uk release and i havent got any issues with it, ive rooted and debloated (i dont know why people are banging on about a russian lite version, its just debloated aswell isnt it)..
Theres been no point really for TWRP so far, i dont know if a custom rom will be released anytime soon

Hi russy23,
thank you for your reply
One thing I didn't understand (language problem...I am no native english speaker):
"Theres been no point really for TWRP so far" means: There are no problem reported
so far flashing a official ROM with the combon of unsigned bootloader and permanent
TWRP?
Do I need to reflash the bootloader?TWRP again?
Sorry for the tutti frutti of questions...I simply fear to lock out myself from the tablet...
Thanks a lot!
Cheers
noriatell

Ive not lost TWRP after i reflashed the official firmware, so it must be a permanent recovery..
well we were given TWRP a while ago to flash custom roms and eveything has gone silent since, for me stock rom debloated is good

russy23 said:
Ive not lost TWRP after i reflashed the official firmware, so it must be a permanent recovery..
well we were given TWRP a while ago to flash custom roms and eveything has gone silent since, for me stock rom debloated is good
Click to expand...
Click to collapse
Hi russy32,
I flashed the 36er ROM...and got an error at the end...but it rebooted fine (so far...did made extensively testing right now, though).
I had to reflash SUPERsu and xposed, but this seems to be quite normal...
Do you know, what triggers this error (Saying "Error flashing <filename of ROM>.zip") ?
When reflashing the 24er ROM there was a problem with a check in one the scripts, which has to be removed by hand before flashing...
I currently dont know of any similiar with the 36er ROM. And that failure was right in the beginning of the process and the ROM.
Is there a way to check whether I am on 36er ROM now (something which is for sure, since the "About" is only a copy of a string...)?
Cheers,
noriatell

If I remember correctly I got an error when installing..but everything was working well after..I installed it through adb. The only way I know to check version is the about section

russy23 said:
If I remember correctly I got an error when installing..but everything was working well after..I installed it through adb. The only way I know to check version is the about section
Click to expand...
Click to collapse
Bad news...
To get a clean install without error I wiped cache, system, Dalvik-cache and system and reinstalled the ROM.
I got errors and a bootloader-loop (stuck in the "Intel" logo).
Now the tablet is charging...I need new power for the next steps.
TWRP is still working.
What had caused this?
How can I get back a clean boot?
Post edit:
I have reapplied my nandroid backup of the 24er ROM. It works so far (It boots). But I have
back the problems I described above.
Question remains:
How can I get a clean install of the 36er ROM?
Cheers,
noriatell

Related

[Q] Unofficial CM11 Problem

Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
Are you on the correct bootloader 10.26.1.18 as is required?
EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
I've not heard of this ocurring (my own tab has been running for a while now; no issues of this sort).
Are you on the latest ROM build (01/29)? Have you flashed the appropriate gapps?
Are you on the latest boot loader?
Any apps installed which could cause issue?
If it happens when plugged in to USB, is isb OK on your PC/Mac?
Have you used titanium backup to restore system level stuff from a non compatible build?
Do this,
Go back to stock (latest release from asus) and observe for an hour or two. Any issues? If not then flash ROM + gapps and wipe. Don't sign in and don't restore apps. Any issues? Then sign in and restore. Any issues? And so on and so forth until.you find the break point.
Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Pershoot once the new CM11 was first flashed the TF701 would freeze during the setup steps well before any 3rd party apps could be installed. After a number of attempts I manage to get through set up and the system becomes a lttle more stable but then freezes after a few more minutes. I can conform that the correct gapps has been flashed using the link on the associated thread and no additional apps except the ones included on the ROM have been flashed. The system freezes without being plugged into the PC via USB and as mentioned before I am coming from sdbags stock rooted 4.3 ROM and have not used titanium back up at all.
A couple of additional point
1) I have tried to reflash sdbags ROM again but it now gets stuck on a bootloop.
2) I noticed that my install of CM11 is not able to access either an SD card placed in the dock or MicroSD placed in the tab despite the system recognising when they are inserted or removed on the task bar.
3) Because the system freezes so quickly it tabvery difficult to transfer a new ROM downloaded to my PC over to the TF701 because the moment it freezes the PC can't communicate with the tab.
Apologies if this reply is a little onerous - any help would be greatly appreciated and thank you both again for your prompt response to my.request for help.
Kind regards,
East
Hold down Volume Down and Power and read the bootloader version from the top left.
EastPatel said:
Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Click to expand...
Click to collapse
That's the wrong BL to be on. I don't believe sdbags' ROM updates BL. You must do it via Asus's update.
Go back to stock recovery and follow asus's procedure to update yourself to their latest 10.26.1.18 (4.3) build.
Dear SD Bags & Pershoot,
Apologies for not responding to your feedback sooner - Its been a busy week at work.
I will follow your advise and update the bootloader via the ASUS website and try to reinstall the rom again over the weekend or early next week and I will update this thread with the results. Once again apologies for not following the instructions more carefully.
Many thanks & kind regards,
East
Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East
EastPatel said:
Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East
Click to expand...
Click to collapse
I have a work around for Sky Go on rooted devices You didn't ask.
PM Please.
Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?
Jrockstar867 said:
Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?
Click to expand...
Click to collapse
Kernel needs recompiling with fixes in it - not a huge job but something I have on my todo list - won't be for a while though.
Is there a thread I can subscribe to to get the latest news??
Sent from my Transformer TF701

[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac

[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.

[Q] Unlock Bootloader B609 + recovery

Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
JellyFox said:
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
Click to expand...
Click to collapse
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
arthios said:
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
Click to expand...
Click to collapse
RootGenius was the first thing i tried. It went up to 66% then i got an error but that was a fully Chinese version.
I just tried it again with the one i found by using Google and it goes up to 72%, then tells me that the root has failed.
Which version did you use?
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
ibeqa said:
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
Click to expand...
Click to collapse
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
JellyFox said:
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
arthios said:
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
Click to expand...
Click to collapse
I disabled my firewall and antivirus and gave RootGenius another try. Normally it goes up to 71% and gives me the error. Now it went to 71%, rebooted and then it gave me the error. The weird part is that right before i get the error, it says the installation is complete.
Moved on to Vroot (which is called Iroot now apparently) . It took a while longer but it wasn't able to do it either.
JellyFox said:
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Z!L0G80 said:
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Click to expand...
Click to collapse
I still didn't get the OTA for B615 yet but thank you for the recovery.
ibeqa said:
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
Click to expand...
Click to collapse
You were right! (not that i every doubted you). I found the problem i had: For some reason, i couldn't boot in bootloader trough my phone BUT i was able to do it with 'adb reboot bootloader'. After making some idiotic mistakes and having to re-flash the stock ROM, I finally was able to install My-RoM v3.3, its rooted, i have Xposed so i am happy
So thank everyone for the help!

Looking to flash OK Pie on P9 Any help would be appreciated.

Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
SideSkroll said:
Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
Click to expand...
Click to collapse
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
zgfg said:
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
Click to expand...
Click to collapse
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
SideSkroll said:
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
Click to expand...
Click to collapse
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
zgfg said:
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
Click to expand...
Click to collapse
Thank you. Thats exactly what I was looking for. I really appreciateyour help.
Btw, no one should have the "hide extensions for known file types" checkbox marked...
Edit: Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
SideSkroll said:
....Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
Click to expand...
Click to collapse
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
SideSkroll said:
Thats exactly what I was looking for...
Click to expand...
Click to collapse
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
zgfg said:
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
Click to expand...
Click to collapse
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
SideSkroll said:
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
Click to expand...
Click to collapse
This small OTA bringing Patch02 over b540 installs even over TWRP (but that was not the case for OTA from eg b535 to b540)
Cannot discuss/compare battery for Omni Pie, since not using Omni
Problem with Camera app does not show on stock Oreo. Even if the app was somehow ported from Huawei, there are maybe problems with integration to Omni.
Various Huawei/Mate models come with different cameras, but there is only one OK Omni ROM (with one Camera app) given to work on all Huawei/Mate models
Btw, somebody else also complained about issues with Camera (and GPS) and decided to go back to stock Oreo.
Similarly, issues you described about black notifications or so must be related to the custom ROM, theme or so.
As a general rule:
- for installing OK ROM, you flash System partition, and nothing else
- you also wipe Data partitiom (containing all your installed apps, incl Magisk Manager, also containing your user settings)
It does not affect any other partition.
Therefore, changes given by NW patch persist - without, you will have (also in that OK ROMs) problems with SIM card(s) and connecting to the network
Also, Magisk, which was flashed to Ramdisk, persists. You must only install Magisk Manager again, because it is user apo, installed to Data partition that was wiped
You must check on the OK side how they advice installing the updates of OK ROMs
(It is questionable if they will get updates any more, since OK team switched to development of ROMs which install over the stock Pie, whereas on P9 you have no stock Pie - only Oreo, and most likely, we will never see stock Pie for P9.
Just check when OK team released last ROM for stock Oreo, and compare with their releases of OK ROMs for stock Pie:
https://openkirin.net/download/
Hence IMO, for updating the OK ROM (if/when it comes), you will again just need to flash its System and to wipe Data (and then to reinstall user apps like Magisk Manager).
Hopefully, you can backup and restore some apps and settings by Titanium.
Whether you don't need to wipe Data for such update - check from the OK support.
On the Open Kirin site you will find Support pages (Faq, HowTo) and also a link to the live Telegram channel

Need persist.img from latest global rom

Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
desertfoxtim said:
Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
Click to expand...
Click to collapse
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
lolo9393 said:
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
Click to expand...
Click to collapse
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
WinBug2 said:
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
Click to expand...
Click to collapse
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
lolo9393 said:
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
Click to expand...
Click to collapse
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
WinBug2 said:
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
Click to expand...
Click to collapse
you need to flash the zip from here through twrp since the fastboot commands dont support zips
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
ANTROBAROTICS said:
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
Click to expand...
Click to collapse
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
gabtit7 said:
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
Click to expand...
Click to collapse
But custom rom can be installed without rooting. So then also safety net will not work ?
Google realeased a new update that checks if the bootloader is unlocked
and the only way to lock it after flashing ROMs is to do a complete format and reinstall the original ROM, it replaces twrp or anything else with the original ROM (miui in our case)
So dont install roms
Okay. Thank you. I just wanted a reason not to install. Now is the end of custom rom I think majority will now no more root or install custom rom because of safety net. Copyright, Security & Privacy are now priority in today's world.
Some other members just found the solution but it supports only Android 10 & 11
[TUTORIAL] WORKING FIX FOR SAFETYNET / CTS PROFILE FAILED
Alright , here we go again . Steps to follow : 1. Open Magisk and select modules tab 2. Install Module for Android 11 - (https://t.me/XiaomiEUCloud/156) For Android 10 - (https://t.me/XiaomiEUCloud/158) from Storage 3. Reboot your Device Done . [emoji3544] UPDATE : NO NEED TO FLASH THIS ON...
xiaomi.eu

Categories

Resources