Hard SPL your phone first before proceeding.
Don't let your battery to discharge completely, if it happens, connect the charger (red led appears), take out the battery (with the charger still connected, red led remains on), put the battery back (orange led appears) and then fast turn the phone on and enter bootloader mode because there the phone is charging even that no led is on.
Google Android kernel build working from NAND memory.
I am glad to introduce you the result of our hard work, based on the android kernel and tinboot bootloader, made by DZO. I am, vsavichev, working on kernel, my friend hrustile- on design and system, and my friend blyha- on the hardware researching and testing part.
HOWTO Installation process.
Doing on the security unlocked phone under your own responsibility, all unlocking info is here: http://forum.xda-developers.com/showthread.php?t=355730
1. Download Nikeimg.7z, archive contain 2 images, for 20 or 16 keys keyboard.
2. Flash it like usual firmware, which means:
2.2 From the SDcard:rename file NIKEIMG16K(20K).nbh to NIKEIMG.nbh and put it to the root of SD card. Make folder named "andboot" in the root of your SD card and put there android build itself, which usually named "androidinstall.tar",if not, rename it. My recommendation is this one, from my friend hrustile : http://www.multiupload.com/OYW85PFMH1. No need to format SD card or remove any files. Turn off your phone and reboot to bootoader mode (e.g. hold CAMERA and POWER buttons) Then phone will detect itself that there is a firmware is on your SD card and will ask your to press POWER button, so press it. Flashing takes about 20 seconds, after it's over pull the battery or press reset.
2.3 From the PC: same procedure exept no need to put NIKEIMG.NBH on the SD card. You need to put it to the folder with flasher on the PC. The rest same as SD card flashing.
But it's not all!!!
3. Turn device on and wait until i says "Hold down Volume Up or DPad Center to launch installer" press and hold central button, you'll see installer menu. If you missed yo press button- reset and press it directly after seeing some output on the screen.
Choose Data & Sys on "(*) NAND" and press Install android, then answer yes twice. Now installation process is started, wait for a minute or so.
4 And at last after installation is over press Quit, first boot takes some time so be patient. Then enjoy your Android.
Click to expand...
Click to collapse
Working:
1. Sound
1.1 Loud speaker
1.2 Voice speaker
1.3 Headset
1.4 Volume adjusting
2. Network
2.2 Bluetooth
2.3 GSM
2.4 GPRS/EDGE/3G
3. Camera
3.1 Main
3.2 Front
4. Hard Buttons
5. Display
5.1 Touch
5.2 Calibration
6. Power Managment
6.1 Hybernation(Sleep)
6.2 Brightness Adjustment
7. Vibration
Works/Not works
Click to expand...
Click to collapse
Here are the last tested images, archive contains 20k and 16k version. I tried some radios, the best one was 1.71k.
Thank you for your hard work！
Darkforcesteam HD2 Forum developed the android, not a simulation. You can contact them, it is possible to obtain some information. If you need darkforcesteam forum account can contact me, my mailbox [email protected]. My English is poor, which is out through Google translations. Sorry.
Can you solve the BUG android on Chinese support it?Thank you
No, chinese is so far from me, im russian.
First, thanks for the advanced work!
I try this last night, and it looks great and smooth, but I have a problem for it.
Mine is Niki100, the screen touch function seems not working properly. I can't finished unlocking the phone, the screen froze after I slide it from left to right.
Anything I can try?
Looks strange for me, if problem is in locked screen only you can unlock it with double pressing of camera button. Then, if screen is still frezed, long press on POWER and then the RED PHONE, sometimes helps. Anyway, the work is very far from over, so i hope there will be a lot of improovments, this build i put here only to show that there is a hope, because all the previos threeds ended so hopeless.
thank u for your work!
but my phone raido is 1.59,your rom can't work on my phone ,if you fix this BUG, it will be perfect!
I don't think it's possible to fix a kernel for a specific radio, but it will be very useful for me, if everyone who tests my build will post the issues wich he will have for sure and the radio version, so i can find the problems, caused by radio and the problems, caused by kernel.
Latest news, now internet connection working.
What's new? Network connection in my cell phone is normal.
Some improvements, now we have all the functions, like under HARET.
How to install?
It seems when I long-pressed the icon (want to delete home screen shortcut), the screen touch works no more. Sometimes It randomly happened when I press several time short-pressed. Other than that, the phone function works fine, and 3g connection is fine too.
vsavichev said:
Some improvements, now we have all the functions, like under HARET.
Click to expand...
Click to collapse
Do we have update for niki16k ?
poyfoster How long does the screen touch work before freeze? Or it happens just after boot? Please, post your radio version, i need it for statistics too.
About 16k update- you are the first to ask, no problem, i'll make one for you in a couple of hours.
It's this a rom?
How to install ? Its only androidinstall.tar and ZIMAGE. There is no default.txt and Haret and initr.gz, I download this package but still dont know how tu run it. Maybe someone can explain me, my device is HTC touch dual NIKKI 20 keys
It works from NAND, wich means your windows mobile will be gone. So you need to be very sure what are you doing before do something.
So if you still want to flash android, you need to put NIKEIMG.nbh on the rootof sd card,
androidinstall.tar and androidupdate.tgz to /andboot/ folder.
Turn off the device, hold CAMERA and POWER buttons, until you get to bootloader, then press power again.
Now press reset or pull battery off, then power on your phone. After splash screens you will see some fast running output, when you see something like "Hold center or volume up button to install" you need to hold center button. All the other stuff is like usual HARET installation, exept you need to put systrm and data on NAND in installer. After install complete, you need to install update before exit.
I need 16K，thanks
HELP VIDEO FOR ANDROID NEWBIES TO HELP THEM CHANGE ROM FROM 2.2 TO 2.3 CM7
http://www.youtube.com/watch?v=RULPBh4cDYU
On demand of some of the very new to android users, im posting a relatively easy to understood upgrade process from 2.2 froyo to 2.3 cm7(custom rom).
http://www.youtube.com/watch?v=MfnoUB8EFOI VIDEO LINK TO THE CM7 ROM DEMO
Remember both these roms(cm7 and miui) are rooted roms.It voids the warranty.
All credits given to the respective developers of the softwares/firmwares shown in this thread.Im just here to make the process more easy to understand.As developers say, DO IT ON YOUR OWN RISK
CM7 FLASHABLE FILE- http://www.mediafire.com/?f90c9utsp8luknd
GOOGLEAPPS PACKAGE- http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
COPY BOTH THESE FILES ON TO UR SDCARD(SAME FOLDER OR SEPERATE FOLDERS) BEFORE U PROCEED ANY FURTHER!
Download this file CLOCKWORK MOD- http://www.mediafire.com/?4mio3rwhhmjw5aq
steps to load cwm recovery
1-Load dell drivers on ur pc which we call adb drivers which i found on my dell mem card folder named ADB_Tethering_Driver.U will find these drivers on this forum also if you dont have it in.
2-setuo fastboot mode on your dell handset
Setting up fastboot:
Turn Device off
Move ringer to UP position
Hold down Power and Volume Down
This will show fastboot mode is on.
3-Download and install cwm
How to Install CWM?
Start recovery.exe and Extract all files
U will see file named Install CWM.bat.
Run that file and now plug ur dell venue to usb cable(venue is still in fastboot mode as we did it before)
Follow instructions on the dos screen to make ur dell venue load cwm recovery.
Your DELL Venue will reboot after installation is finished
4-Then you can see DELL logo after reboot.
Immediate you press Volume UP+DOWN
5-Once you're in the CWM recovery before you flash the ROM zip, you need to :
a. Wipe data/Factory Reset
b. Wipe Cache Partition
c. Wipe Dalvik Cache
Use vul + - key to toggle the menu and go to INSTALL UPDATE option in that menu.Again on next screen u will be asked to choose update file selection.Option name i forgot may be "INSTALL UPDATE FROM SDCARD".
Select the CM7 file which you downloaded earlier and copied to sdcard.Select and click CAMERA button to start installation.It will take about a minute or two to complete installation.
5-As installation finishes, you will see the msg - UPDATE COMPLETED.Then u need to go back to the previous menu and select REBOOT SYSTEM NOW.Finish that step.
Thats done!You are into the world of smoother, faster , interactive dell venue cm7 2.3 rom!
You wont be able to cnnect to any of google applications at this time.
To enable google account and apps, u need to follow all the earlier steps and again go into the cwm recovery mode and install the GAAP packge which u have downloaded with cm7.The process will be same...update from sdcard,select gaap file and reboot.It should not be a big deal.
option2:Also u can go to cm7 settings menu and find option to boot into cwm recovery in dell phone itself(no need of pc to run cwm).However u need the GOOGLEAPPS FLASHABLE file on ur sdcard to flash it in cwm recovery in any case...option1 or option2.
Same process needs to be followed to install another update for ussd/mmi codes.
Download this package http://mirror2.streakdroid.com/manii/misc/USSD Fix/update-USSDfix-2.zip and flash it in same way as gapps was done.This would solve ur problem of ussd codes( * # kind of calls) as well.
NOTES:
ONE MAY FACE REDUCED BATTERY BACKUP IN THIS CM7 ROM,
I HAVE FOUND A WAY FOR IT, BY USING SETCPU application WHICH COMES IN THIS ROM AS BUNDLED.
MY SETCPU SETTINGS ARE:
1-START ON BOOT CHECKED
2-PROFILES ENABLED CHECKED. TWO PROFILES ADDED FIRST IS "SCREEN OFF" SET TO "POWERSAVE" AND SECOND PROFILE "IN CALL" SET TO "CONSERVATIVE"
*IF U GET STUCK AT BOOT AFTER INSTALLING ZIP OF CM7 FILE FROM CWM, U SHUD SIMPLE FOLLOW 2 STEPS. DO AL DATA WIPE,CACHE WIPE AND DATA RESET.THEN FLASH CM7 AGAIN WITHOUT RESTARTING PHN.THIS WILL SOLVE BOOT LOOPING PROBLEM IF ARISES.
THESE SETTINGS GIVE ME EXTRA BATTERY BACKUP OF ABT 3/4HOURS.
hirentherock555 said:
On demand of some of the very new to android users, im posting a relatively easy to understood upgrade process from 2.2 froyo to 2.3 cm7(custom rom).
Remember both these roms(cm7 and miui) are rooted roms.It voids the warranty.
All credits given to the respective developers of the softwares/firmwares shown in this thread.Im just here to make the process more easy to understand.As developers say, DO IT ON YOUR OWN RISK
CM7 FLASHABLE FILE- http://www.mediafire.com/?f90c9utsp8luknd
GOOGLEAPPS PACKAGE- http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
COPY BOTH THESE FILES ON TO UR SDCARD(SAME FOLDER OR SEPERATE FOLDERS) BEFORE U PROCEED ANY FURTHER!
steps to load cwm recovery
1-Load dell drivers which we call adb drivers which i found on my dell mem card folder named ADB_Tethering_Driver.U will find these drivers on this forum also if you dont have it in.
2-setuo fastboot mode on your dell handset
Setting up fastboot:
Turn Device off
Move ringer to UP position
Hold down Power and Volume Down
This will show fastboot mode is on.
3-Download and install cwm
How to Install CWM?
Download this file - http://www.mediafire.com/?4mio3rwhhmjw5aq
Start recovery.exe and Extract all files
U will see file named Install CWM.bat.
Run that file and now plug ur dell venue to usb cable(venue is still in fastboot mode as we did it before)
Follow instructions on the dos screen to make ur dell venue load cwm recovery.
Your DELL Venue will reboot after install finished
4-Then you can see DELL logo
Immediate you press Volume UP+DOWN
5-Once you're in the CWM recovery before you flash the ROM zip, you need to :
a. Wipe data/Factory Reset)
b. Wipe Cache Partition
c. Wipe Dalvik Cache
Use vul + - key to toggle the menu and go to INSTALL UPDATE option in that menu.Again on next screen u will be asked to choose update file selection.Option name i forgot may be "INSTALL UPDATE FROM SDCARD".
Select the CM7 file which you downloaded earlier and copied to sdcard.Select and click CAMERA botton to start installation.It will take about a minute or two to complete installation.
5-As installation finishes, you will see the msg - UPDATE COMPLETED.Then u need to go back to the previous menu and select REBOOT SYSTEM NOW.Finish that step.
Thats done!You are into the world of smoother, faster , interactive world of dell venue cm7 2.3 firmware!
You wont be able to cnnect to any of google applications at this time.
To enable google account and apps, u need to follow all the earlier steps and again go into the cwm recovery mode and install the GAAP packge which u have downloaded with cm7.The process will be same...update from sdcard,select gaap file and reboot.It should not be a big deal.
Click to expand...
Click to collapse
Thanks
Super cool and simple explaination quite helpful. Will try this.
But are there any bugs in this update?
Also if possible is there any rollback method if we get stuck or mobile bricks?
I did not find any bugs in cm7 as yet...havent tried miui rom yet.
CM7 is supercool rom.You would love it.Its 10times better than the 2.2 inbuilt rom dell give.
Rollback would require stockroms(which r available on his forum i think).
Unbricking method post is also given in this forum.Check and do the diligence at ur own risk.
hirentherock555 said:
I did not find any bugs in cm7 as yet...havent tried miui rom yet.
CM7 is supercool rom.You would love it.Its 10times better than the 2.2 inbuilt rom dell give.
Rollback would require stockroms(which r available on his forum i think).
Unbricking method post is also given in this forum.Check and do the diligence at ur own risk.
Click to expand...
Click to collapse
Worked as said
Thanks a ton mate
Also just trouble was needed to download google apps which was never done by me ever
Asphalt 6 HD roxs now
Fantastic!
So atlast u installed google apps rom also na?After flashing with cm7?
Tell me how is camera performance in ur dell device?
On gsmarena i saw many people praising the camera but i found it really awefully bad!
Wondering oif cam in bad in my handset only?
hirentherock555 said:
Fantastic!
So atlast u installed google apps rom also na?After flashing with cm7?
Tell me how is camera performance in ur dell device?
On gsmarena i saw many people praising the camera but i found it really awefully bad!
Wondering oif cam in bad in my handset only?
Click to expand...
Click to collapse
Yes flashed with google apps zip
Camera is good to very good 8 MP
HD video also is good
i have updated the step by step process with additional mmi code solution also into the last paragraph.U can check it.
I dnt knw why, my cam is giving bad results with backcover on and better result when i take cover off.Can u check in ur cam result of both ways? and let me knw?
hirentherock555 said:
i have updated the step by step process with additional mmi code solution also into the last paragraph.U can check it.
I dnt knw why, my cam is giving bad results with backcover on and better result when i take cover off.Can u check in ur cam result of both ways? and let me knw?
Click to expand...
Click to collapse
Sure
Guess you must try cleaning the cover lence once
Still will update you on the same
hirentherock555 said:
Fantastic!
So atlast u installed google apps rom also na?After flashing with cm7?
Tell me how is camera performance in ur dell device?
On gsmarena i saw many people praising the camera but i found it really awefully bad!
Wondering oif cam in bad in my handset only?
Click to expand...
Click to collapse
took it to test today
used it as normal as i always do
but battery drain observed was high than stock
half a day by 3 noon my fone waz 20 %
unplugged at 7am
on stock at this time i would be 60 %
just use opera and whatsapp
any suggestions?
will clearing battery stats help?
heard it makes things worst
here are some suggestions:
1: in stock rom when wifi is on and connected to a router, and u went away from in wifi area, it will stop searching for wifi.When u will enter in same wifi zone again, u wont get auto connected to wifi.
Whereas in cm7, after leaving wifi area with wifi on(and connected), upon returning to wifi area again, u will find venue connected to that wifi network automatically.
This means wifi is continuously looking for connection in cm7 but not in stock rom.Make appropriate changes to try and enhance battery life.
2:SETCPu application
Use this application to save battery.I used it today and felt the difference.
3:Set brightness levels to zero rather than auto.
We have to change our habits of using phones to save battery.Thats a hard fact!
Above all should help though.
hirentherock555 said:
here are some suggestions:
1: in stock rom when wifi is on and connected to a router, and u went away from in wifi area, it will stop searching for wifi.When u will enter in same wifi zone again, u wont get auto connected to wifi.
Whereas in cm7, after leaving wifi area with wifi on(and connected), upon returning to wifi area again, u will find venue connected to that wifi network automatically.
This means wifi is continuously looking for connection in cm7 but not in stock rom.Make appropriate changes to try and enhance battery life.
Click to expand...
Click to collapse
I am not using wif fi
I am on 2G EDGE mate
2:SETCPu application
Use this application to save battery.I used it today and felt the difference.
Click to expand...
Click to collapse
Any suggested settings?
3:Set brightness levels to zero rather than auto.
We have to change our habits of using phones to save battery.Thats a hard fact!
Click to expand...
Click to collapse
Thats not an issue done that
1ST CLICK ON SETCPU - RUN ON BOOT CHECK
GO TO PROFILES AND ADD 2 PROFILES
1ST SELECT "SCREEN OFF" AND SELECTOR SCALLING "POWERSAVE"
2ND SELECT "IN CALL" AND SELECT SCALLING "CONSERVATIVE"
iM USING THESE SETTINGS TODAY.
cELL FULLY CHARGED AND DISCONNECTED POWER AT 8.30AM MORNING.
iTS 5PM NOW AND BATTERY LEFT IS STILL56%
i HAVE WIFI ALWAYS ON AS I HAVE ROUTER AT HOME.
i HAVENT USED MUCH OF INTERNET THOUGH.
AS PER BATTERY USE MENU TLL NOW FROM MORNING,
DISPLAY IS USED FOR 1.3HRS.
VOICE CALL DATA SHOWS 52MINUTES
WIFI USED FOR 8.30 HOURS AS WELL.
i THINK ITS DECENT BATTERY BACKUP IF I KEEP THESE SETTINGS.
YES PERFORMANCE SEEMS TO BE SLIGHTLY LESS WITH SETCPU.ABT 10-15% LAG IN PERFORMANCE.BUTS I WILL TAKE THAT.
hirentherock555 said:
1ST CLICK ON SETCPU - RUN ON BOOT CHECK
GO TO PROFILES AND ADD 2 PROFILES
1ST SELECT "SCREEN OFF" AND SELECTOR SCALLING "POWERSAVE"
2ND SELECT "IN CALL" AND SELECT SCALLING "CONSERVATIVE"
iM USING THESE SETTINGS TODAY.
cELL FULLY CHARGED AND DISCONNECTED POWER AT 8.30AM MORNING.
iTS 5PM NOW AND BATTERY LEFT IS STILL56%
i HAVE WIFI ALWAYS ON AS I HAVE ROUTER AT HOME.
i HAVENT USED MUCH OF INTERNET THOUGH.
AS PER BATTERY USE MENU TLL NOW FROM MORNING,
DISPLAY IS USED FOR 1.3HRS.
VOICE CALL DATA SHOWS 52MINUTES
WIFI USED FOR 8.30 HOURS AS WELL.
i THINK ITS DECENT BATTERY BACKUP IF I KEEP THESE SETTINGS.
YES PERFORMANCE SEEMS TO BE SLIGHTLY LESS WITH SETCPU.ABT 10-15% LAG IN PERFORMANCE.BUTS I WILL TAKE THAT.
Click to expand...
Click to collapse
Thanks will try that
Also wanted to know can we flash dell stage UI 1.6 in this rom?
It is there here somewhere but I dont know as havnt tried
No idea abt stage ui as i really didnt like it and neither want it.
U amy try searching forum for tht.
Google Apps with audio/video ability
Gapps with gtalk audio/video ability
http://goo.im/gapps/gapps-gb-20110828-newtalk-signed.zip
Has anyone tried the above?
havent trid.also the link u shown there does not work.
Try uploading on medafire.
It would be great if all users here can press SUBMIT THREAD button on top of the page so that this thread can feature on xda home page and people get to know about it.
talk2 (the one with video chat) wont fully work on the V because it has no FFC.
It might otherwise work to recieve video/voice though, but it cant send video.
TheManii said:
talk2 (the one with video chat) wont fully work on the V because it has no FFC.
It might otherwise work to recieve video/voice though, but it cant send video.
Click to expand...
Click to collapse
Wont the back camera work for this?
just curious
Did the setcpu settings help u?
hirentherock555 said:
Did the setcpu settings help u?
Click to expand...
Click to collapse
Was on your settings before I re formatted my cell.
Was going okish..
But when I reformatted it, made sure the battery was full and then wiped battery stats.
Now I am onn without setcpu, goes for 10 to 13 hrs max with few calls, whatsapp always on, mails, etc.
Will go on with this for a month. Then check with setcpu if it gives any difference.
Hi.
I found this tutorial on the internet that works 100% for those who have Zenfone 5 with fake firmware. In my case i used the last firmware V2.21.40.44 without flashing older version and then Update to the last one. The original tutorial is as below.
I purchased the Zenfone A501CG 16GB 2GB RAM and I am very happy with this phone.
One of the things I like is the dual-sim setup. Besides the obvious dual-sim functions it lets you set which sim you are going to use for data or you can be prompted every time. As the second sim, I popped in a 3 mobile broadband data-only sim and it worked straight away without manually setting up the APN etc.
I have been a Galaxy S series fan for a few years and I was worried about switching to ASUS but the excellent Asus GUI (General User Interface) is very neat and works flawlessly. I was expecting a heavily customised (and buggy) GUI but I am very pleased that it turned out to be very smooth with plenty of features and customisation options.
Now the bad part.
The phone is shipped from China and they advertise it as having a WW (WorldWide) firmware installed prior shipping, which it is in part true.
I want to say that I have nothing against phones from China as most of the electronic equipment is manufactured over there nowadays however the phone firmware is a fake WW.
I don't know how they did it but they managed to install a WW 2.99.40.6 ASUS firmware over a CN sku.
This means that the phone originally was a Chinese handset subsequently converted to WW. The resulting phone is indeed in English (or any language you choose to setup), it has access to GooglePlay store, Gmail accounts and all the rest and it works no problem over here. Don't get me wrong, it's still a great kit. You wouldn't notice anything wrong however one of the major flaws of this particular setup is that it will not update over OTA (or manually).
OTA (On The Air) updates works that you simply click “check for system update” and the phone will connect to ASUS and upgrade itself to the latest version available for your handset (JellyBean, KitKat etc...).
ASUS has implemented an alternative way to upgrade its phones: you go the ASUS website, select you model, region/language etc and you can manually download the system update file.
Save this file on your phone internal storage, next time you reboot the phone Android will see that there is an update file waiting to be installed and it will ask you whether you want to upgrade.
You can download this file directly using your phone or if you are on a strict data usage budget (these updates files are about 700 MB in size) using a computer then copying it over to your phone internal storage by connecting the phone to your computer via USB cable.
OK, that's OTA and manual upgrade covered... this phone with WW 2.99.40.6 however will not update, nor over OTA nor by manually placing the firmware file on the internal storage.
I thought, well... why not simply download the latest from ASUS and install it overwriting the existing one? This way I will have the latest clean official up to date firmware... right?
Wrong, the phone will not update simply because its firmware 2.99.40.6 is “too new”, a firmware from the future...
Confused? Let me explain, this is the clever part: in February 2015 ASUS released the (currently) latest firmware update for Zenfone A501CG which is the 2.21.40.44.
Now let me point out that firmware versions always go up, for example:
1.16.40.7 (that was in 2014)
1.17.40.17 (still 2014)
1.18.40.8
1.18.40.9
2.19.40.18
2.21.40.30 (December 2014)
and the latest 2.21.40.44
You noticed that the numbers go UP with every release.. the highest the newest.
Now, if you look at the fake firmware installed on the phone (2.99.40.6) you will see that the 2.99.40.6 (look at the “2.99” bit), is even higher than the very latest 2.21.40.44 so the phone simply will not “downgrade” from 2.99.40.6 to 2.21.40.44. That's because with these android phones you cannot downgrade, only upgrade.
This is how the sellers prevent you from upgrade your phone. You are simply locked to this firmware... but why???
The only reason I can think of is that the operating system has some spyware, tracker or some advertising bloatware they don’t' want you to get rid of upgrading the firmware. This is the only possible explanation in my opinion.
When you upgrade firmware (from JellyBean to KitKat for example) files are kept, apps and their settings are kept and updated, user settings are transferred over. So all the unwanted pre-installed crapware would pass through the new version anyway so why the need to lock the firmware? Perhaps there is something deep down in the system that has been tampered with and will not survive a firmware update. That's what I think.
At the beginning after receiving this phone I didn't spot the fake firmware right away. As many of us do when they have a new phone, I checked for update via OTA, there was none. Actually, the System Update function crashed every time I checked for updates but I didn't bother looking any further into this matter because I was very pleased with the phone, it looked good and performed well.
Nothing seems to be wrong apart from the System Update glitch and Gallery crashing quite often.
It was after a couple of days of use when I started receiving unsolicited popup messages asking me to install additional apps that I started wondering if there was something wrong with my phone after all. These popups used to come up when the phone was idle, 4 popups at a time and sometimes right after rebooting.
I have been installing on the Zenfone exactly the same apps I had on my Galaxy S2 so I knew how these apps behave and what to expect from them so at the beginning I thought it was the ASUS GUI o some other pre-installed app. No, these popups were an issue related to the new phone.
I immediately thought that a reputable brand like ASUS (I own other ASUS products since 2005 and always been happy) wouldn't (or shouldn't) annoy new customers with these kind of nuisance, this would inevitably drive customers away so I decided to run some virus/spyware checks. Nothing major was found and the popups still occurred at least 3 times a day. That was day 4 on my Zenfone.
Almost forgot: the phone came rooted. Apart from the obvious advantages this also means that any virus scan can be performed deep into the system with administrative privileges. Having your phone rooted also means that it is not covered by ASUS warranty but that's another issue...
At this point I decided that it was time to do something about it. First I did a factory reset but this didn't work as this returned the phone at its original state when I took it out of the box 4 days before.
So I decided that I had to force the phone to “downgrade” to a previous ORIGINAL firmware then re-upgrade it installing the latest firmware from the ASUS website and this is how.
First of all you need two tools:
1) the USB drivers for ASUS phones fro Windows. You can download them from the ASUS website or search the internet for “ASUS Zenfone 5 Windows Drivers”.
2) the ADB package, I used the one provided here:
http://forum.xda-developers.com/showthread.php?t=2588979
This one actually provides the drivers too. Feel free to browse the internet and find the appropriate source but you will be downloading more or less the same file.
After you installed these two tools you need something called “Recovery Image”, there are some here:
https://www.mediafire.com/folder/cq6wwpya68azb/ZenFone_5_recovery
in my case I used this one: 2.19.40.18_ww_recovery.img
and finally you need an original firmware from the ASUS website here:
http://www.asus.com/uk/Phones/ZenFone_5_A501CG/HelpDesk_Download/
in my case I downloaded this one: UL-ASUS_T00F-WW-2.20.40.13-user.zip
So what we are going to do here is:
we will downgrade the phone from the current WW 2.99.40.6 to WW 2.19.40.18
then install WW 2.20.40.13
and finally we will perform a OTA update to the latest firmware.
The whole process should take about 1 hour.
Please note that this method only works if:
1) your Zenfone 5 is a A501CG (T00F or T00J).
2) your current firmware is WW 2.99.40.6 but it will probably work with other “fake” firmwares too, you just need a different set of files (please note the “WW” bit is IMPORTANT, if your firmware is CN, CHT or TW this will not work and you will damage your phone).
3) your phone is rooted (if you are still reading this it probably is but check if you have an app called SuperSU with a yellow triangle).
4) USB debugging is enabled (do a google search to see how this can be done, enabling debugging mode takes 20 seconds).
..basically this will work if you have received the same phone I got.
If any of the above 4 points is not clear please run a quick google search. There is plenty of literature out there however not much literature on the internet covers what we are going to do now or if there is it is all scattered around various sites. That's why I am posting this, all info in one place.
Procedure:
Find the ADB folder on your computer and place there the file 2.19.40.18_ww_recovery.img you downloaded from mediafire.
The UL-ASUS_T00F-WW-2.20.40.13-user.zip you downloaded from ASUS is a ZIP archive, open it, extract the file fastboot.img and place it in the ADB folder.
Put the UL-ASUS_T00F-WW-2.20.40.13-user.zip you downloaded from ASUS in the ADB folder too (do not extract this file, just place the ZIP archive in the ADB folder).
At the end in the ADB folder (apart from the adb files that were already there) you should have the following files:
UL-ASUS_T00F-WW-2.20.40.13-user.zip
2.19.40.18_ww_recovery.img
fastboot.img
We start with the phone turned OFF. Make sure it has some battery left (more than 50%) turn your Zenfone on in Fastboot Mode (this can be done by pressing and holding at the same time the power Button and Volume UP buttons... together).
Connect the phone to the computer.
In the ADB folder on your computer open a command prompt window (called a CMD window). This can be done by pressing (on your PC keyboard) Shift then right-clicking with the mouse anywhere in the empty space in the ADB folder.
Now in the resulting CMD (black) window write the following command (exactly as it is written here):
fastboot flash fastboot fastboot.img
hit Enter. Then write:
fastboot flash recovery 2.19.40.18_ww_recovery.img
hit Enter and wait until completion.
Do not disconnect your phone and do not close the CMD (black) window on your computer but reboot your phone in Fastboot Mode (there should be a command on the phone screen “reboot fastboot”), navigate up and down with the volumes keys and confirm the selection with the power button).
Once you are back in Fastboot Mode go to Recovery. Now you should see the Android logo with a red triangle, press at the same time the Volume UP and the Volume DOWN keys to reveal a hidden menu (try pressing and holding the + and – keys several times if it doesn't come up the first time).
In this menu you need to go to Upload Firmware from ADB (or something similar) and confirm by pressing the power key.
Now, go back to your computer and in the CMD window type the following command:
adb sideload UL-ASUS_T00F-WW-2.20.40.13-user.zip
and hit Enter.
At this point your phone will start loading the original WW-2.20.40.13 we downloaded from the ASUS website. This will take some time, in my case it took about 45 minutes.
Once this is done you can reboot the phone and you will have a brand new Zenfone 5 with a WorldWide (real) 2.20.40.13 firmware, the one before the last one. Now we want to upgrade to the very latest (which is the best for Zenfone 5 in my opinion).
To upgrade now you have two options:
1) start using the phone right away and upgrade to the latest 2.21.40.44 via OTA or...
2) manually download the 2.21.40.44 from ASUS to your computer, place it on your phone internal storage and let the phone update at the next reboot.
In my case I choose the second option, it doesn't really make any difference however...whichever option you choose after the upgrade to the latest firmware you should perform two final last steps. This is to clean up, optimise and make sure the phone system runs smoothly from now on.
Very quickly...
Step 1: (AFTER you upgraded to the last firmware 2.21.40.44 either via OTA or manually) you should reboot to Fastboot Mode, select Recovery and “Wipe Cache Partition”. Wait until completion then...
Step 2: reboot your phone in normal mode and before starting to register and installing all apps go to Settings, Backup & Reset and do a Factory data Reset. Obviously this will wipe all your apps and settings but, as I suggested before, you didn't install anything yet.
Final tip: if you have an external SD card you already used on another phone or even in the Zenfone before the upgrade I would suggest reformat it before starting using it on your “new” phone. Many apps leave things behind on the SD that newly installed versions of the same apps don't like.
After this last two steps your phone is ready, no more suspicious junk and a 100% original ASUS system.
An optional step would be to root your phone again (upgrading firmware disables root or superuser) and put to sleep some of the pre-installed ASUS apps you don't need.
With root (device administrative) privileges you could un-install them but disabling them is enough.
I personally disabled some googleplay services like books, music, movies, games, newsstand, google+ (I never used them) then the following pre-installed apps: weather, asus backup, cloudprint, drive, feedback, hangouts, myasus, pc link, setup wizard, share link, webstorage, what's next, remote link.
But that's me, I don't use these apps and they have the habit to autostart with the phone and stay in the background eating systems resources and battery juice even if you haven't used them in a year.
Ah... rooting your device also allows you to reach and delete the batterystats file dramatically increasing battery performance.
VERDICT:
My opinion is that THE PHONE IS EXCELLENT, it really exceeded my expectations, the only downside is the fake firwmware which spoils the fun until you learn how to fix it. The original ASUS software is well balanced, polished and smooth and not at all bloated. Plenty of customizations too.
Post Scriptum:
Before buying this phone I checked some reviews and I learnt that apparently the battery was weak and wouldn't last a whole day. After 3 weeks of everyday use I have to say that this depends on what you do with your phone (obviously...).
By default ALL is enabled when you take it out of the box because the manufacturer is trying to give you the best (visual, probably) experience.
Without being conservative you have to find out and disable what is eating up your battery and you don't need.
The trick is to use the phone as it is for a whole charge (say, from 100% to 10% but already at around 50% you get an idea of what's going on) then before putting under charge go to Settings, Battery and check the statistic data.
You will see that that nice weather widget giving you the temperature and the rain forecast is sucking 40% of your juice because it is constantly updating... is it worth it? Push sync of 5 email accounts is really necessary..?? Real time travel updates..?
When you learn how to manage your device and what is running and when you will see that the battery life will stretch 3 times over. This applies to all smart phones.
Reading the Zenfone reviews another issue seemed to be quite common: the wifi would disconnect..! Now, that's an issue...! I wouldn't want to buy a phone with a dodgy wifi.
Truth is that if you enable the Power Saver in Ultra-saving Mode the wifi will cut off when the screen is turned off (this is also written in small letter on the on/off button). Obviously you won't receive any notification during scree-off time and connectivity will resume as soon as you turn the screen on.
Luckily to save extra battery life it's not all-or-nothing there is a Power Saving scheme (the third one) which is called Customized Mode where you can pick what you want to run or stop during power saving mode.
Good Job
Hay, nice info and tutor.. my problem is same with you.
Can you make video tutorial please?
Thanks.
enea009 said:
Hi.
I found this tutorial on the internet that works 100% for those who have Zenfone 5 with fake firmware. In my case i used the last firmware V2.21.40.44 without flashing older version and then Update to the last one. The original tutorial is as below.
I purchased the Zenfone A501CG 16GB 2GB RAM and I am very happy with this phone.
One of the things I like is the dual-sim setup. Besides the obvious dual-sim functions it lets you set which sim you are going to use for data or you can be prompted every time. As the second sim, I popped in a 3 mobile broadband data-only sim and it worked straight away without manually setting up the APN etc.
I have been a Galaxy S series fan for a few years and I was worried about switching to ASUS but the excellent Asus GUI (General User Interface) is very neat and works flawlessly. I was expecting a heavily customised (and buggy) GUI but I am very pleased that it turned out to be very smooth with plenty of features and customisation options.
Now the bad part.
The phone is shipped from China and they advertise it as having a WW (WorldWide) firmware installed prior shipping, which it is in part true.
I want to say that I have nothing against phones from China as most of the electronic equipment is manufactured over there nowadays however the phone firmware is a fake WW.
I don't know how they did it but they managed to install a WW 2.99.40.6 ASUS firmware over a CN sku.
This means that the phone originally was a Chinese handset subsequently converted to WW. The resulting phone is indeed in English (or any language you choose to setup), it has access to GooglePlay store, Gmail accounts and all the rest and it works no problem over here. Don't get me wrong, it's still a great kit. You wouldn't notice anything wrong however one of the major flaws of this particular setup is that it will not update over OTA (or manually).
OTA (On The Air) updates works that you simply click “check for system update” and the phone will connect to ASUS and upgrade itself to the latest version available for your handset (JellyBean, KitKat etc...).
ASUS has implemented an alternative way to upgrade its phones: you go the ASUS website, select you model, region/language etc and you can manually download the system update file.
Save this file on your phone internal storage, next time you reboot the phone Android will see that there is an update file waiting to be installed and it will ask you whether you want to upgrade.
You can download this file directly using your phone or if you are on a strict data usage budget (these updates files are about 700 MB in size) using a computer then copying it over to your phone internal storage by connecting the phone to your computer via USB cable.
OK, that's OTA and manual upgrade covered... this phone with WW 2.99.40.6 however will not update, nor over OTA nor by manually placing the firmware file on the internal storage.
I thought, well... why not simply download the latest from ASUS and install it overwriting the existing one? This way I will have the latest clean official up to date firmware... right?
Wrong, the phone will not update simply because its firmware 2.99.40.6 is “too new”, a firmware from the future...
Confused? Let me explain, this is the clever part: in February 2015 ASUS released the (currently) latest firmware update for Zenfone A501CG which is the 2.21.40.44.
Now let me point out that firmware versions always go up, for example:
1.16.40.7 (that was in 2014)
1.17.40.17 (still 2014)
1.18.40.8
1.18.40.9
2.19.40.18
2.21.40.30 (December 2014)
and the latest 2.21.40.44
You noticed that the numbers go UP with every release.. the highest the newest.
Now, if you look at the fake firmware installed on the phone (2.99.40.6) you will see that the 2.99.40.6 (look at the “2.99” bit), is even higher than the very latest 2.21.40.44 so the phone simply will not “downgrade” from 2.99.40.6 to 2.21.40.44. That's because with these android phones you cannot downgrade, only upgrade.
This is how the sellers prevent you from upgrade your phone. You are simply locked to this firmware... but why???
The only reason I can think of is that the operating system has some spyware, tracker or some advertising bloatware they don’t' want you to get rid of upgrading the firmware. This is the only possible explanation in my opinion.
When you upgrade firmware (from JellyBean to KitKat for example) files are kept, apps and their settings are kept and updated, user settings are transferred over. So all the unwanted pre-installed crapware would pass through the new version anyway so why the need to lock the firmware? Perhaps there is something deep down in the system that has been tampered with and will not survive a firmware update. That's what I think.
At the beginning after receiving this phone I didn't spot the fake firmware right away. As many of us do when they have a new phone, I checked for update via OTA, there was none. Actually, the System Update function crashed every time I checked for updates but I didn't bother looking any further into this matter because I was very pleased with the phone, it looked good and performed well.
Nothing seems to be wrong apart from the System Update glitch and Gallery crashing quite often.
It was after a couple of days of use when I started receiving unsolicited popup messages asking me to install additional apps that I started wondering if there was something wrong with my phone after all. These popups used to come up when the phone was idle, 4 popups at a time and sometimes right after rebooting.
I have been installing on the Zenfone exactly the same apps I had on my Galaxy S2 so I knew how these apps behave and what to expect from them so at the beginning I thought it was the ASUS GUI o some other pre-installed app. No, these popups were an issue related to the new phone.
I immediately thought that a reputable brand like ASUS (I own other ASUS products since 2005 and always been happy) wouldn't (or shouldn't) annoy new customers with these kind of nuisance, this would inevitably drive customers away so I decided to run some virus/spyware checks. Nothing major was found and the popups still occurred at least 3 times a day. That was day 4 on my Zenfone.
Almost forgot: the phone came rooted. Apart from the obvious advantages this also means that any virus scan can be performed deep into the system with administrative privileges. Having your phone rooted also means that it is not covered by ASUS warranty but that's another issue...
At this point I decided that it was time to do something about it. First I did a factory reset but this didn't work as this returned the phone at its original state when I took it out of the box 4 days before.
So I decided that I had to force the phone to “downgrade” to a previous ORIGINAL firmware then re-upgrade it installing the latest firmware from the ASUS website and this is how.
First of all you need two tools:
1) the USB drivers for ASUS phones fro Windows. You can download them from the ASUS website or search the internet for “ASUS Zenfone 5 Windows Drivers”.
2) the ADB package, I used the one provided here:
http://forum.xda-developers.com/showthread.php?t=2588979
This one actually provides the drivers too. Feel free to browse the internet and find the appropriate source but you will be downloading more or less the same file.
After you installed these two tools you need something called “Recovery Image”, there are some here:
https://www.mediafire.com/folder/cq6wwpya68azb/ZenFone_5_recovery
in my case I used this one: 2.19.40.18_ww_recovery.img
and finally you need an original firmware from the ASUS website here:
http://www.asus.com/uk/Phones/ZenFone_5_A501CG/HelpDesk_Download/
in my case I downloaded this one: UL-ASUS_T00F-WW-2.20.40.13-user.zip
So what we are going to do here is:
we will downgrade the phone from the current WW 2.99.40.6 to WW 2.19.40.18
then install WW 2.20.40.13
and finally we will perform a OTA update to the latest firmware.
The whole process should take about 1 hour.
Please note that this method only works if:
1) your Zenfone 5 is a A501CG (T00F or T00J).
2) your current firmware is WW 2.99.40.6 but it will probably work with other “fake” firmwares too, you just need a different set of files (please note the “WW” bit is IMPORTANT, if your firmware is CN, CHT or TW this will not work and you will damage your phone).
3) your phone is rooted (if you are still reading this it probably is but check if you have an app called SuperSU with a yellow triangle).
4) USB debugging is enabled (do a google search to see how this can be done, enabling debugging mode takes 20 seconds).
..basically this will work if you have received the same phone I got.
If any of the above 4 points is not clear please run a quick google search. There is plenty of literature out there however not much literature on the internet covers what we are going to do now or if there is it is all scattered around various sites. That's why I am posting this, all info in one place.
Procedure:
Find the ADB folder on your computer and place there the file 2.19.40.18_ww_recovery.img you downloaded from mediafire.
The UL-ASUS_T00F-WW-2.20.40.13-user.zip you downloaded from ASUS is a ZIP archive, open it, extract the file fastboot.img and place it in the ADB folder.
Put the UL-ASUS_T00F-WW-2.20.40.13-user.zip you downloaded from ASUS in the ADB folder too (do not extract this file, just place the ZIP archive in the ADB folder).
At the end in the ADB folder (apart from the adb files that were already there) you should have the following files:
UL-ASUS_T00F-WW-2.20.40.13-user.zip
2.19.40.18_ww_recovery.img
fastboot.img
We start with the phone turned OFF. Make sure it has some battery left (more than 50%) turn your Zenfone on in Fastboot Mode (this can be done by pressing and holding at the same time the power Button and Volume UP buttons... together).
Connect the phone to the computer.
In the ADB folder on your computer open a command prompt window (called a CMD window). This can be done by pressing (on your PC keyboard) Shift then right-clicking with the mouse anywhere in the empty space in the ADB folder.
Now in the resulting CMD (black) window write the following command (exactly as it is written here):
fastboot flash fastboot fastboot.img
hit Enter. Then write:
fastboot flash recovery 2.19.40.18_ww_recovery.img
hit Enter and wait until completion.
Do not disconnect your phone and do not close the CMD (black) window on your computer but reboot your phone in Fastboot Mode (there should be a command on the phone screen “reboot fastboot”), navigate up and down with the volumes keys and confirm the selection with the power button).
Once you are back in Fastboot Mode go to Recovery. Now you should see the Android logo with a red triangle, press at the same time the Volume UP and the Volume DOWN keys to reveal a hidden menu (try pressing and holding the + and – keys several times if it doesn't come up the first time).
In this menu you need to go to Upload Firmware from ADB (or something similar) and confirm by pressing the power key.
Now, go back to your computer and in the CMD window type the following command:
adb sideload UL-ASUS_T00F-WW-2.20.40.13-user.zip
and hit Enter.
At this point your phone will start loading the original WW-2.20.40.13 we downloaded from the ASUS website. This will take some time, in my case it took about 45 minutes.
Once this is done you can reboot the phone and you will have a brand new Zenfone 5 with a WorldWide (real) 2.20.40.13 firmware, the one before the last one. Now we want to upgrade to the very latest (which is the best for Zenfone 5 in my opinion).
To upgrade now you have two options:
1) start using the phone right away and upgrade to the latest 2.21.40.44 via OTA or...
2) manually download the 2.21.40.44 from ASUS to your computer, place it on your phone internal storage and let the phone update at the next reboot.
In my case I choose the second option, it doesn't really make any difference however...whichever option you choose after the upgrade to the latest firmware you should perform two final last steps. This is to clean up, optimise and make sure the phone system runs smoothly from now on.
Very quickly...
Step 1: (AFTER you upgraded to the last firmware 2.21.40.44 either via OTA or manually) you should reboot to Fastboot Mode, select Recovery and “Wipe Cache Partition”. Wait until completion then...
Step 2: reboot your phone in normal mode and before starting to register and installing all apps go to Settings, Backup & Reset and do a Factory data Reset. Obviously this will wipe all your apps and settings but, as I suggested before, you didn't install anything yet.
Final tip: if you have an external SD card you already used on another phone or even in the Zenfone before the upgrade I would suggest reformat it before starting using it on your “new” phone. Many apps leave things behind on the SD that newly installed versions of the same apps don't like.
After this last two steps your phone is ready, no more suspicious junk and a 100% original ASUS system.
An optional step would be to root your phone again (upgrading firmware disables root or superuser) and put to sleep some of the pre-installed ASUS apps you don't need.
With root (device administrative) privileges you could un-install them but disabling them is enough.
I personally disabled some googleplay services like books, music, movies, games, newsstand, google+ (I never used them) then the following pre-installed apps: weather, asus backup, cloudprint, drive, feedback, hangouts, myasus, pc link, setup wizard, share link, webstorage, what's next, remote link.
But that's me, I don't use these apps and they have the habit to autostart with the phone and stay in the background eating systems resources and battery juice even if you haven't used them in a year.
Ah... rooting your device also allows you to reach and delete the batterystats file dramatically increasing battery performance.
VERDICT:
My opinion is that THE PHONE IS EXCELLENT, it really exceeded my expectations, the only downside is the fake firwmware which spoils the fun until you learn how to fix it. The original ASUS software is well balanced, polished and smooth and not at all bloated. Plenty of customizations too.
Post Scriptum:
Before buying this phone I checked some reviews and I learnt that apparently the battery was weak and wouldn't last a whole day. After 3 weeks of everyday use I have to say that this depends on what you do with your phone (obviously...).
By default ALL is enabled when you take it out of the box because the manufacturer is trying to give you the best (visual, probably) experience.
Without being conservative you have to find out and disable what is eating up your battery and you don't need.
The trick is to use the phone as it is for a whole charge (say, from 100% to 10% but already at around 50% you get an idea of what's going on) then before putting under charge go to Settings, Battery and check the statistic data.
You will see that that nice weather widget giving you the temperature and the rain forecast is sucking 40% of your juice because it is constantly updating... is it worth it? Push sync of 5 email accounts is really necessary..?? Real time travel updates..?
When you learn how to manage your device and what is running and when you will see that the battery life will stretch 3 times over. This applies to all smart phones.
Reading the Zenfone reviews another issue seemed to be quite common: the wifi would disconnect..! Now, that's an issue...! I wouldn't want to buy a phone with a dodgy wifi.
Truth is that if you enable the Power Saver in Ultra-saving Mode the wifi will cut off when the screen is turned off (this is also written in small letter on the on/off button). Obviously you won't receive any notification during scree-off time and connectivity will resume as soon as you turn the screen on.
Luckily to save extra battery life it's not all-or-nothing there is a Power Saving scheme (the third one) which is called Customized Mode where you can pick what you want to run or stop during power saving mode.
Click to expand...
Click to collapse
im stack at the final step
adb sideload UL-ASUS_T00F-WW-2.20.40.13-user.zip
and hit Enter.
then i get
error: device not found.
Any ideas?
plus my device in fast boot has no option reboot fastboot but "reboot droidboot" wich i used...
thnx in advance for everything
I m stuck at status 7 installation aborted....
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
5. The stock rom my phone has is based on Android 8.1 (8.1.0 OPM1.171019.011) to be exact, for rom version refer to reply. I've tried different versions of gcam, but none of 'em has worked for me. Normal camera app works fine, nothing I've encountered yet.
These are the versions I've tried -
* F1v9.5_6.2.030.apk (Couldn't install as 6.2 is only supported by android pie)
* MGC_6.1.021_XCAMBase_F1_v5a.apk (Installed and worked, details below)
* MGC_6.1.021_Potter_v7.1_san1ty.apk (Installed, didn't open)
* MGC_6.1.021_Potter_v7_san1ty.apk (Installed, didn't open)
On photo, the camera lags like I'm playing a game at 2-3 fps, same for other photo related options. Except for panaroma, photo sphere, lens blur, these I didin't had problem with. Except panaroma pic never showed up in camera app or gallery. In video it doesn't lag, so recording normal video was fine. But when I recorded a slo mo video, it lagged after the recording, inside & out the camera app. Inside gcam the audio was fine but outside it was muffled. By outside I mean gallery app & vlc player.
I may try other versions but each app is so big.
Gurkirat_Singh said:
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
Click to expand...
Click to collapse
sir, you never mention which version you are on ? since Boot is locked so definately MIUI but which one? global/beta/Eu/ Stable/chine etc?
anways..
Answer for 1, - No you have to redownload it, the Fastboot Rom consist of few extra files like persist and recovery and if they are update you must use the latest one. however via twrp you can take system/data/ and other partitions backup if you want...
for 2. after 72hours, goto dev option and try enabling oemunlock, it will give you warning but do it, come out of dev option and go in and do it again, repeat until the UNLOCK setting stays on UNLOCK, (don't know why it is, but this is how it is,,,, ) , later verify your miui account and sim, keep signed in. download unlocker and sign- in and try unlocking the device (make sure all qualcom drivers are installed)
for 2 again, This is very strange, ONE OF ITS KIND error I AM hearing , I honestly thought this bug is ONLY custom rom related! , you see Poco f1, Beryllium uses MODIFIED VENDOR IMAGE ( can be found at) https://mirror.akhilnarang.me/MIUI/beryllium/.
now these modified vendor images by MIUI dumps logs on data/data/netstat (specially if you are USB TETHERING on 3g, ... you will start suddent System UI reboots and some com.android.xyz processes crashing errors and if you toggle Airplone mode 3g/4g or usb tethering from quick setting , device either hung or system ui restarts or device reboots.
now this error is always in all custom roms due to vendor image
solution? DELETE all files from data/data/netstat and reboot (rooted device on custom rom)
for locked device (unrooted) you may have to flash updated version of miui to fix this bug!
Once you unlock device take latest vendor image ( i am using 9.6.27.9-0 , it has better battery life) and flash custom rom...
for 2 again,,,, some users are complaing that miui10.3.6 alters fastboot commands! and twrp no longer works! , make sure you don't flash miui10.3.6,
for no3,, i don't use facial unlock feature, i will study more and will get back to u if relevent.
for 4
Open MIUI Security App.
Tap on Data Usage Tool.
Tap on Restrict Data Usage.
Now find out those data hunger apps and restrict them by tapping on the green tick.
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Gurkirat_Singh said:
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Click to expand...
Click to collapse
sir Gurkirat_Singh
1. sir you are on Miui9.6 which is based on oreo.I have personally updated till 10.0.03 and have all the fastboot command working fine.
you may download miui9.6.22 (a bit updated version from what you are currently on) from
http://en.miui.com/thread-3995650-1-1.html ( both Recovery (1.6gb) & Fb rom (2.5gb) as backup.
2. under Developer options , poco f1 has this trick that OEM UNLOCK doesnt stick on UNLOCK and keeps coming to default once after you exit Developer option. on my 5th attempt it finally stick to UNLOCK and i was able to unlock the device from unlocker Tool.
3. I havent removed my poco sticker from back (yet), put 9h class, bought extra skin my self and book cover too so yes I second that. I always protect my devices like part of me , even the retired ones are sleeping in boxes with proper covers and unused accories!,
now, update your rom and try again to toggle 3g/4g usb tethering. 99% chances are its software issue! and i have faced this issue many times and its my 5th month with device so i havent noticed any hardware damage or performance / speed problems yet... so don't worry. YES few kernels affect network connectivity, however I am on Optimus Drunk kernel on Havoc 2.8 and its working like a charm!
-about file manager issue, can you try the same with FX File Explorer? and report back plz
4.if you restrict globally then miui will only allow system apps to use data in background as and when needed. MIUI won't allow facebook/whatsapp and other VOIP callers to work in the background. Once in restricted mode on miui9 on RN5pro, I used to miss call on whatsapp unless i wake the device up and notifications starts appearing that i have many whatsapp miss calls!, this feature went even worse on rn5pro when i was on dual sim, miui use to prefer carier sim over data sim always! so yes miui has strict data usage control.
5. i am unable to find 5th question plz help
few screen shots of my poco f1 on HAVOC2.8 / OD kernel build20190820 / magisk19.3 / gapps nano
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Gurkirat_Singh said:
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Click to expand...
Click to collapse
sir
1. I never read any such method so far where you can reverse engineer the extracted files in partitions and pack them back as fastboot rom. and to think of it thats almost impossible because stockroms usually comes with digitally signed by vendors ensuring no foul play.
2. once your 72hrs over, just unlock the oem unlock switch from Dev option, verify sim of on your mi account, download the unlock tool, login using same mi account, hit unlock, after success, the device will BOOT on POCO logo and "UNLOCKED" will start appearing (always) and all data partition, internal storage will be wiped! so make sure you take backup!
2a. with me on custom rom it wasn't a sure thing but it used to happend randomly when least expected.
5. on oreo , GCAM version came in sep2016 worked for me and later ones are for pie and kept crashing (please check old version on apkmirror)
@YasuHamed Thanks for all the help.
5. I did found a version that is working fine for now. But the features I was interested in was super res zoom, night mode, slo mo etc. Super rez wasn't that impressive(seemed similar to stock zoom), night mode either, slo mo still doesn't work properly and phone heats up, even when I'm not using too old of a version of gcam. Even the stock cam app took some good shots with zooming.
And if those features will work better with pie version then IDK what to say cause that new version would come with better stock cam having slo mo, night mode and all that shiz if not everything. So I'm kinda thinking is this gcam port really relevant? It drastically changed image quality with my RN3 but I don't see that now.
Edit: Also I wanted to say that my phone was working fine now i.e. no reboots after closing mobile data or wifi or switching. But you know what they say don't celebrate too soon. As soon as I used usb tethering the problem arised again, I wasn't able to it for 2 days as my PC wasn't booting. Same reason why I wasn't able to reply to you earlier.
Not only this, this whole bugged situation has started to irritate me a lot. Just today I was trying to run flash on my android. And even on the supported browser, it just wouldn't show up. I really hope after I unlock this device, all of these bugs would go away after the data gets deleted, or I'm gonna be more disappointed.
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Gurkirat_Singh said:
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Click to expand...
Click to collapse
please consider upgrading to MIUI10.3.x , download the complete recovery rom and name it as update.zip and put it in download folder and open updater and call the rom from there , and flash it, I suggest CLEAN FLASHING so all the data will be deleted!
plz take backup!
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Gurkirat_Singh said:
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Click to expand...
Click to collapse
frankly i never used my poco on miui either on 9 nor on 10 ,
the day I got, I placed unlock request and after 3-4 days, I unlocked my device and put it on HAVOC and since then my experience is based on custom roms but i did flash miui 10 in between just to have a taste of it! and came back to havoc in a day or two, hence i never deeply tested these feature.
however I do know that modified vendore have created usb tethering problems throughout devices
https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Gurkirat_Singh said:
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Click to expand...
Click to collapse
-sir, most of your observations are pertaining to V9.6.14.0.OEJMIFD, where I am not on MIUI hence I will wait for other members to step in and share their views about them.
- you can always use "Disable-Force-Encryption-Treble" from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389, when flashing rom (clean flash, FORMAT DATA) to disable encryption on kernel level.
- since Twrp official doesnt support OTA so if you call recovery from updater, it wont work! you may have to use Orange Fox (oct/nov2018) version which had OTA support or better flash full rom after downloading desired version from https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
- what are you looking is from different world of android devices, such as TEMP ROOT, IVORY ROOT (sony xperia on android 5.1) days only! when nothing used to be changed but just to gain access of certain partition temporarily, temp root techniques used to apply to extract DRM KEYS. ITs not the case here hence you will have to root your device properly!
- about gpu, i never tried but you can used app such as FK kernel manage or Kernel Auditor to play with your GPU accordingly
- twrp usually ask keep system readonly whenever flashed new room its standard warning to avoid any bootloops since Twrp doesn't know you will be flashing kernel and/or disabling dm varity soon. so it warns you.
- don't worry POCO is FREE from ARB4 $hit so when page said ROLLED BACK, it means those version were recalled back for some buggs and an update released soon after!
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
please view my replies sir
Gurkirat_Singh said:
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
I flashed "DisableForceEncryption_Treble_v18.0.zip" and it worked/works, but I always flash before magisk., the current version is Magisk19.3 hence I recomend you to use the updated version, 16.7 is obsolete long back. However if 19.3 may give you bootloops then the max you can go back is Magisk18.0 (since after 18.1, Magisk started using different Script language unknown to some recoveries. However if BOTH (your recovery and Magisk are latest, it should work just fine
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
once on RN5p I tried updating OTA via twrp, it never booted to update hence I recomend you to download full recovery rom 1.8gb, of the build you want and flash it via twrp
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
plz try any root checker and see
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
fk kernel manager or kernel Auditor does support editing build prop, apart from many tweaks for GPU and Cores. the video shows a simple edit in order to think your device is some other version of Galaxy to trick samsung app ; however The boy didn't explain why he just didn't install the already downloaded apk file from fortnite website ?
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
if you are flashing MIUI From twrp, and DON"T wana ROOT then yes you should never allow system modification because then device will never boot in to system due to DM-Verity. However if you are rooting yoru device, try reading Magisk Lines, It always patch fstab and disable Dm-verity, once its disabled /system parition permision wont be verified on boot. So when you boot in to twrp and you know you are going to flash Magisk, you can ALLOW SYSTEM MODIFICATION swip
on Custom Roms it doesn't matter, because twrp never ask such question. "allow system modification" is only limited to StockRoms
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
the next version above ROLLED BACK one is the bug fixed. (now i don't know what exactly were they) . Also MIUI forums for devices always announce updates! you can google
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
well probably this is the bug of this version 9.6.14 hence you should upgrade atleast to 9.6.20 in order to compare
Click to expand...
Click to collapse
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
6. Again you didn't tell me how'd you find those roms!?
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
Sorry for the late reply, got a little busy.
sir ..........................
Gurkirat_Singh said:
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
1- Yes I flashed DFET before Magisk19.3 - and why i didn't use the third file, i remember in post one user confirmed this particular one working for him (atleast) so i downloaded that one.
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
2- ideally this is the case with recoveries which doesn't support OTA, OrangeFox based on OLD version of TWRP does support OTA , I NEVER TRIED but worth reading the post. you should find it in the Poco Development section
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
3- I use THIS ONE
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
4- To get general IDEA about altering Build.Prop, The video is Good! however you can not assume Samsung Modded Android over MIUI's one! also It seems the boy in the video has Android7 where Miui Poco is atleast on 8.1, there is huge difference!
The only way to find out whether any type of build.prop (EVEN ON CUSTOM ROMS) will WORK or NOT on POCO; is to Try and find out yourself.
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
5- Once twrp changes the /System as writable, cannot be undone from Twrp itself - since you have magisk16.7 as you mention earlier the dm-varity is turned off and you are booting normally.
-unlocking means, your device can accept fastboot commands to Alter various Partitions developed by Third Party! /recovery /system /vendor /oem etc
-Rooting is Gaining /system access in Android OS to perform Forbiddon and/or Unsafe Commands / Apps etc
- now your question about security , i will simply say! its HIGHLY UNSECURE to unlock your device & Root it!, there is debate about SeLinux Permissions to be Permissive or Enforcing , SELinux in enforcing mode is considered to be little better and secure but Permissive mode means any command can be run even by hacker to gain your /system access ! REFERENCE
- unlocked bootloader is also very unsafe! anyone can just flash any compatable recovery and atleast WIPE your data!
HENCE this is what i say to all my fellow friends and mates in general! if you are CONCERN security privacy , NEVER ROOT your device! or keep two devices, one being as family device! for fotos, emails contacts etc! and play with the other!
- about warranty! every region has different rules! my country's Xiaomi centre doesn't cover any brick devices because here they are alreadly selling many Redmi fones on UNLOCKED mode! directly from china!
6. Again you didn't tell me how'd you find those roms!?
https://c.mi.com/oc/miuidownload/index select poco and see officially available rom
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
EDL ? you mean fastboot rom flashing via miflasher!, thats not edl! to trigger EDL you must have
1. authorized Xiaomi Account
2. back panel of poco to be opened and short test point to put device in EDL
Sorry for the late reply, got a little busy.
Click to expand...
Click to collapse
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
................................................................................................................................................................................
Gurkirat_Singh said:
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
we i am glad , we have a winner here
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
Temporarily , LOS is suspended but even unofficial roms till mid August are very stable ! you should try! , hoever Pixel is very popular too, on deeper level what diferences you may find thats only user can discover over time. there is no direct answer to this question! LOS is driven from CynogenMod which was on AOSP wehre Pixel is CAF based, so the difference comes on Kernel Level this means CAF rom may have different Hardware performance / behaviour when compare to AOSP based roms (and vice versa). I am not sure about multirom as a daily driver, yes I would like to try for fun but wont keep it.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
on Poco i have tried Nitrogen, Omni, MoKee, BootLeggers, CrDroid, LOS and Havoc..
BootLeggers is pretty stable rom! however CrDroid is outstanding because the developer @gwolfu is more active and releases many updates (sometimes 3-4 in a month). Crdroid has serious level of customization (dirtyUnicorn) and you can change the look of your rom in every possible way you imagine!
so the question is WHY am I on Havoc, well the simple answer is both Crdoid and Havoc Offers serious level of DU customization & variations found on deeper level. some items which crdroid doesn't offer i found in Havoc so I stick to it, moreoever I feel the font and resolution by default in havoc is next to pixel where in Crdoid you manualy have to fix (dpi and font)
now I am on havoc2.8 but I am using Optimus Drunk Kernel (which is also used by CRDROID) - the developer of havoc2.8 offers SHADOW kernel which as I said I feel is not very battery effcient (atleast for me, others can disagree)
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
-keeping system Read only OR swipe to allow /system as writable is on Recovery Level ,
- when you keep system on READY ONLY on recovery Level and later flash magisk, the module magisk modify the /system permission which twrp doesn't know!
-if you "allow system modification on twrp level the /system is now set on writable permission by twrp, and magisk is a module which is always set to alter /system partition permission irespective of Global policy on recovery level
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
now this let me think a little bit, the only possible explaination (in theory) I found is
- when you flash all or clean flash all, its not necessary that /recovery partition is first erased by miflasher! and recovery.img file has many folders including setting folder! so miflasher and later by you simply there was swaping of recoveries, the Tree was always there! when you reflashed twrp! try to do this way
Code:
fastboot erase recovery
fastboot flash twrp.img
this should erase any previous left over data and settings
try and let me know!
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
i simply google / web search rom number with device name with code name like Miui9.6.20 fastboot download poco f1 beryllium and google suggest few popular results which usually works for me!
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
I would say 9.6.14 had bug so reflashing didnt help! as I said before, consider upgrading atleast to 9.6.20
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
till MiMax
-holding THREE buttons for 30 seconds used to trigger edl mode
-miflasher simply identify EDL mode and used to flash the beryllium fastboot rom
the question is why they stopped?
well fastboot rom when extracted, hackers can simply alter and repack the img files! YOU CAN EVEN place twrp as "recovery.img" in extracted folder miui will flash twrp thinking its vendor recovery! and the device in EDL mode will accept it..
this was serious security risk! so they capped EDL mode in both ends
- miuiflasher needs AUTHORISED ACCOUNT
- DEVICE won't enter in edl mode unless you remove back cover and under batter wire you short two motherboard points with thin wire or tweaser! (and immediately connect usb calbe to system)
now what can you do?
1. use older version of Miflasher which doesnt verify rom
2. user altered rom of specific build or time to WAKE UP your BRICKED device!
I have never done it so you need to investigate and use your poco as gunie pig to test these methods after REMOVING Back Panel (HIGHLY NOT RECOMENDED
or take device to authorised Mi Dealer and let them EDL for you!
Click to expand...
Click to collapse