This is a debloated/slightly modified ROM. There are NO ASUS apps, and only the bare minimum Google apps. I don't use any of the Fit apps, so they have been removed, but I believe they can be easily reinstalled through the PlayStore. Everything on the watch is significantly faster, except the Bluetooth call lag still exists on 4G, like it does on every device lately. I don't notice the bluetooth lag when the phone and watch are connected to WiFi. There is no watch face installed, so install one from the PlayStore after it boots. I pulled the boot animation from the developer preview, and the clock works during boot. It's pretty sexy.
Within the zip are the boot and recovery files as well, which include TWRP and a patched boot.img for Magisk. You'll need to sideload the latest Magisk Manager to have root access.
DIRECTIONS:
Download and extract Sparrow_7.1.1_Debloat
Boot into fastboot mode.
fastboot -w (This wipes the device, which is HIGHLY recommended.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.simg
I highly recommend starting with fastboot -w to wipe the device. If you run into any issues at all and didn't wipe before install, then wipe and try again before posting issues. Also, pay close attention to the SIMG in system.simg. Type it exactly as it's posted, or copy and paste it. The SIMG is important lol.
Anyone running this ROM should look into this mod by @LeeonLee. Everything is noticeably smoother and lightning fast. I haven't gotten any Bluetooth lag since I implemented it. https://forum.xda-developers.com/ze...parrowaw2-0-enabling-cores-gpu-boost-t3800427
Let me know what you guys think and if I should add/remove anything. I plan to add some more tricks if I update the ROM, including some speed tweaks. Happy Flashing!!!
Appears to work fine here.
CVertigo1 said:
This is a debloated/slightly modified ROM. There are NO ASUS apps, and only the bare minimum Google apps. I don't use any of the Fit apps, so they have been removed, but I believe they can be easily reinstalled through the PlayStore. Everything on the watch is significantly faster, except the Bluetooth call lag still exists on 4G, like it does on every device lately. I don't notice the bluetooth lag when the phone and watch are connected to WiFi. There is no watch face installed, so install one from the PlayStore after it boots. I pulled the boot animation from the developer preview, and the clock works during boot. It's pretty sexy.
Within the zip are the boot and recovery files as well, which include TWRP and a patched boot.img for Magisk. You'll need to sideload the latest Magisk Manager to have root access.
DIRECTIONS:
Download and extract Sparrow_7.1.1_Debloat
Boot into fastboot mode.
fastboot -w (This wipes the device, which is HIGHLY recommended.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.simg
I highly recommend starting with fastboot -w to wipe the device. If you run into any issues at all and didn't wipe before install, then wipe and try again before posting issues. Also, pay close attention to the SIMG in system.simg. Type it exactly as it's posted, or copy and paste it. The SIMG is important lol.
Anyone running this ROM should look into this mod by @LeeonLee. Everything is noticeably smoother and lightning fast. I haven't gotten any Bluetooth lag since I implemented it. https://forum.xda-developers.com/ze...parrowaw2-0-enabling-cores-gpu-boost-t3800427
Let me know what you guys think and if I should add/remove anything. I plan to add some more tricks if I update the ROM, including some speed tweaks. Happy Flashing!!!
Click to expand...
Click to collapse
Hi...I install this rom and the mod leeonlee, my watch have high battery drain, I do not know what to do
Did the battery life get significantly worse compared to stock 2.0? There was no noticeable difference in battery life for me. It was always horrible on 2.0 for me.
I have been running this for almost 3 weeks with @LeeonLee mod, and I haven't gotten any significant Bluetooth lag for calls. Before his mod, it wasn't uncommon that my phone would ring for 5 seconds before the watch showed me someone was calling. I mainly use my watch for riding my motorcycle, so any call lag is a big deal when I can't see who is calling.
I also haven't gotten the "not available" message when using voice commands since the mod.
Hello, I'm using still the stock rom, just rooted + performance patch, watch last 2 days, even 3 days when not used so intensively.
LeeonLee said:
Hello, I'm using still the stock rom, just rooted + performance patch, watch last 2 days, even 3 days when not used so intensively.
Click to expand...
Click to collapse
Maybe I should look into the build.prop mods I added from another watch. Perhaps it's causing excessive battery usage. It could also be that my watch battery is degraded.
which version of magisk manager and how sideload it? i'm little bit noob with adb
Here is a much easier way if you don't know adb too well. Download the latest Magisk installer zip from the Magisk thread onto your PC. I personally am using the 16.4 beta at this time. The Magisk Manager is included in the Magisk zip. Assuming you have TWRP installed, boot into recovery using *adb reboot recovery* or swipe from the top right when booting. The watch is recognized as a storage drive when it's in recovery. Then you can copy the Magisk zip from you PC to your watch, and install it with TWRP. This will give you the latest Magisk and Magisk Manager.
CVertigo1 said:
Here is a much easier way if you don't know adb too well. Download the latest Magisk installer zip from the Magisk thread onto your PC. I personally am using the 16.4 beta at this time. The Magisk Manager is included in the Magisk zip. Assuming you have TWRP installed, boot into recovery using *adb reboot recovery* or swipe from the top right when booting. The watch is recognized as a storage drive when it's in recovery. Then you can copy the Magisk zip from you PC to your watch, and install it with TWRP. This will give you the latest Magisk and Magisk Manager.
Click to expand...
Click to collapse
Never thought about using TWRP to transfer the zip, I just simply pushed it via adb and then rebooted to TWRP to install magisk zip.
BTW, after installing recovery.zip, boot.zip, magisk.zip, I rooted and setup the OnDemand script. It now is much smoother and don't see any noticeable lags. I downloaded System Info Wear to check that the script is actually working. It shows all four cores running at 787Mhz. Kudos to @LeeonLee for the script setup!! Many thanks also to @CVertigo1 !! I also decided to do what @LeeonLee mentioned in regards to stock rom staying put. I wasnt too eager to wipe current system just yet
hi guys... the smartwatch finally is usable.. but i have a question, have the wrist gestures been removed?
Just want to say that I've been using this ROM for a few weeks now, along with the core unlock mod. And it is amazing. The watch is so much more fluid. And with my rather light usage (always on, no gestures) I still get a full day out of the battery. I'm also glad all the extra bloat is gone. No apps I'll never use and no watchfaces I never set.
If you are thinking about switching from stock, highly recommended.
Thanks @CVertigo1
mastermoon said:
hi guys... the smartwatch finally is usable.. but i have a question, have the wrist gestures been removed?
Click to expand...
Click to collapse
Wrist gestures are still there, you just have to turn on that setting under Gesture settings.
bleached45 said:
Just want to say that I've been using this ROM for a few weeks now, along with the core unlock mod. And it is amazing. The watch is so much more fluid. And with my rather light usage (always on, no gestures) I still get a full day out of the battery. I'm also glad all the extra bloat is gone. No apps I'll never use and no watchfaces I never set.
If you are thinking about switching from stock, highly recommended.
Thanks @CVertigo1
Click to expand...
Click to collapse
I really appreciate the kind words. That's exactly what I was going for. I'm not big into searching through a hundred apps to find the few I need, so I prefer my devices to be very militaristic. If I need Fit apps, or any other app, I'll install them separately. They don't need to live in the system. I stripped as much as I could without causing bootloops. I may be able to pull a few more out for the next ROM upload, and I'll also include @LeeonLee mods.
despite my limited modding skills I managed to do everything without doing any damage .. a big thank you to @CVertigo1 and @LeeonLee for the great work ..
Hope @CVertigo1 will be able to port a zenwatch3 rom on 2 one day...
Can I use this rom for wren?
I have just recently installed this on my watch, and it is very nice! The only thing that I noticed is that the pedometer (through Google Fit) does not seem to count the steps I am taking, is this related to some of the files be removed or is it just Google?
I'm not working at the moment but I want to send you a donation as soon as I can. I wanted to thank you because your debloated ROM managed to get my watch booting up once again for the first time in nearly a year. You deserve a donation because you saved me from spending money I don't wanna waste on an entirely new watch.
Is there any way to install some watchfaces stock after installing this Rom?
jnelsoninjax said:
I have just recently installed this on my watch, and it is very nice! The only thing that I noticed is that the pedometer (through Google Fit) does not seem to count the steps I am taking, is this related to some of the files be removed or is it just Google?
Click to expand...
Click to collapse
Is the pedometer really not working on this rom?
djleor said:
Is the pedometer really not working on this rom?
Click to expand...
Click to collapse
nope, but everything else works great.
Related
PadFone S - Android 5.0 Lollipop released
ASUS PadFone S Firmware: V12.2.2.21 Only for WW SKU (Android 5.0)
ASUS said: Some apps been removed some been added
the braver; any luck to upgrade... please share your experience, screenshots, is there any problems or issues?
http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+S&p=29&s=1
At first I was constantly getting an error saying process.android.acore had crashed. I went into settings, apps, and then to the all tab and cleared the data for contacts and contacts storage. Now, the error is gone. Scrolling in Firefox, seems smoother. I like the quick apps you can launch from notifications. So far, I like it.
I like it too, it seems like the docking station got louder and smoother.
Camera is smoother too.
4k I went from 12 fps (at&t) to 20-24 fps (PFS)
Chromecasting works natively.
You get better battery life because of two reasons. Lollipop (Project Volta) and Asus autostart manager. This is what other android manufacturers should include in the phones themselves. (it can prevent an app from running it and it does that without root)
Lastly better performance
Edit: I like to also point out that fm radio works. Im surprised. Maybe asus disabled it by default because it didnt work in stock.
The only problem for me is getting additional call settings to work.
It would say error with reading SIM card even though LTE works, calling works etc.
This would bother me maybe not you guys because somehow my "network default" is private calling and a private number tends to not get picked up or not answered. (its been like that on my old phone)
I want it to be set on "show number" but it has to check SIM but it doesn't work.
If anyone else has the same problem of doing that the only work around is to dial *82 and the phone number after that so you will be recognized on caller id.
In other words if you can call and your number shows up like normal then you are likely not going to use the additional call settings.
The second issue if you are on at&t is there is no band 17 support.
2 and 4 work fine. Great for T-Mobile
The only way of getting back 17 is restoring from an EFS backup from twrp
Other than that, nothing is acting weird and unstable compared to the at&t version.
Months of waiting and this is fing awful.
Worst design descisions and tonns of bloatware...
so far so good!
I didn't revert back to the factory recovery, nor did I do a full wipe.
Flashed dirty TWRP!
shigileeni said:
PadFone S - Android 5.0 Lollipop released
ASUS PadFone S Firmware: V12.2.2.21 Only for WW SKU (Android 5.0)
ASUS said: Some apps been removed some been added
the braver; any luck to upgrade... please share your experience, screenshots, is there any problems or issues?
http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+S&p=29&s=1
Click to expand...
Click to collapse
Dirty flashed with TWRP recovery a few days ago (when the link popped up in the ASUS PadFone S forums). Have been testing it thoroughly. OK so far, nothing that earth shaking.
I use this as a tablet for the most part, update works, no hiccups. Video playback and audio both seem a little bit more crisp in station. WiFi stable. Battery balance good.
Going to do a full TWRP data format, then clean flash with Gapps and SuperSU to see if it gets a performance boost.
XPOSED works just fine on this updated ROM.. Lots of Lollipop whistles and bells work with the activated modules. (You must be rooted of course.)
A tweaked kernel would really help here. They safe zoned the Krait 400 CPU to its lowest point, and I'm sure that it will go much higher, 2.8-3.0Ghz perhaps. The Adreno 330 should be able to go to dance @675.
More later.
blambo said:
Dirty flashed with TWRP recovery a few days ago (when the link popped up in the ASUS PadFone S forums). Have been testing it thoroughly. OK so far, nothing that earth shaking.
I use this as a tablet for the most part, update works, no hiccups. Video playback and audio both seem a little bit more crisp in station. WiFi stable. Battery balance good.
Going to do a full TWRP data format, then clean flash with Gapps and SuperSU to see if it gets a performance boost.
XPOSED works just fine on this updated ROM.. Lots of Lollipop whistles and bells work with the activated modules. (You must be rooted of course.)
A tweaked kernel would really help here. They safe zoned the Krait 400 CPU to its lowest point, and I'm sure that it will go much higher, 2.8-3.0Ghz perhaps. The Adreno 330 should be able to go to dance @675.
More later.
Click to expand...
Click to collapse
I was thinking about tweaking CPU performance but unlike the stock AT&T rom, this one is relatively stable and doesn't make my Padfone X heat up like a furnace. I've had this on all night and into this morning. I've been really happy with the results and maybe AT&T should take notice since whatever they did to this ROM (or whatever ASUS did with it) is why this unit didn't sell. Reminds me of the Pantech Element. Decent device but it was locked down heavily and crashed constantly under Honeycomb. Once ICS came out a few years ago, it acts normally and works better than it ever did before.
I actually just went into TWRP and installed this ZIP without GAPPS and used the WW one. At first it didn't work but the second time, I did a full wipe which removed data and cache partitions. Since then, it booted and has since. Instead of using ADB, I just copied it to a micro SD card and installed it from there.
No real issues except for one minor one where I turned off an option and the tablet piece stopped working until I rebooted it. But no random resets and no extremely hot phone this time. I remember with the old ROM that it got so hot that I had to put it on the air conditioning vent and then the refrigerator because I thought it was going to burn through the plastic.
Plus, now it's unlocked (I'm using T-Mobile now and have LTE coverage) and the dock works.
---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------
nameless517 said:
Months of waiting and this is fing awful.
Worst design descisions and tonns of bloatware...
Click to expand...
Click to collapse
This is how the older ROM was also for the Padfone S when I installed it. If you root it, can't you just remove these apps?
Either way, it's stable, unlocked, and the dock works so I can live with bloatware. Maybe it's because I'm from the USA and all of our phones have this but unlike Windows Phone, I can uninstall them (This is one advantage Windows Phone has. You can actually remove all of the bloatware from the machine easily without much effort).
Here's hoping this keeps up.
Lauren
alissa914 said:
I was thinking about tweaking CPU performance but unlike the stock AT&T rom, this one is relatively stable and doesn't make my Padfone X heat up like a furnace. I've had this on all night and into this morning. I've been really happy with the results and maybe AT&T should take notice since whatever they did to this ROM (or whatever ASUS did with it) is why this unit didn't sell. Reminds me of the Pantech Element. Decent device but it was locked down heavily and crashed constantly under Honeycomb. Once ICS came out a few years ago, it acts normally and works better than it ever did before.
I actually just went into TWRP and installed this ZIP without GAPPS and used the WW one. At first it didn't work but the second time, I did a full wipe which removed data and cache partitions. Since then, it booted and has since. Instead of using ADB, I just copied it to a micro SD card and installed it from there.
No real issues except for one minor one where I turned off an option and the tablet piece stopped working until I rebooted it. But no random resets and no extremely hot phone this time. I remember with the old ROM that it got so hot that I had to put it on the air conditioning vent and then the refrigerator because I thought it was going to burn through the plastic.
Plus, now it's unlocked (I'm using T-Mobile now and have LTE coverage) and the dock works.
---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------
This is how the older ROM was also for the Padfone S when I installed it. If you root it, can't you just remove these apps?
Either way, it's stable, unlocked, and the dock works so I can live with bloatware. Maybe it's because I'm from the USA and all of our phones have this but unlike Windows Phone, I can uninstall them (This is one advantage Windows Phone has. You can actually remove all of the bloatware from the machine easily without much effort).
Here's hoping this keeps up.
Lauren
Click to expand...
Click to collapse
Well, I guess I just got used to CM12.1, clean and fast. Official 5.0 looks too much cluttered and IMHO ugly, and everything felt weird. Got back to CM.
any lollipop BSOD guys? my padfone s was getting BSOD after 1 week smooth operation. black screen with only notif and navigaton bar visible. always need to restart after that and becoming more often even after i did factory reset and reinstalling the firmware.
is it really lollipop bugs or what? cause it happened almost no clear reasons. first i guess it was caused by my smart cover apps that automatically lock unlock screen if i closed my flip cover but even in a couple of minutes after fresh and clear reinstalling firmware without installing any apps it happened again and again. i also read about this bug up to 5.1 release in nexus 5 if i am not mistaken.
highbud said:
any lollipop BSOD guys? my padfone s was getting BSOD after 1 week smooth operation. black screen with only notif and navigaton bar visible. always need to restart after that and becoming more often even after i did factory reset and reinstalling the firmware.
is it really lollipop bugs or what? cause it happened almost no clear reasons. first i guess it was caused by my smart cover apps that automatically lock unlock screen if i closed my flip cover but even in a couple of minutes after fresh and clear reinstalling firmware without installing any apps it happened again and again. i also read about this bug up to 5.1 release in nexus 5 if i am not mistaken.
Click to expand...
Click to collapse
Im still fine after 10 days of operation. Keep in mind im really using a padfone x that is converted.
What ever it is you should do the downgrade then upgrade again. It shouldn't hurt anything. Just follow the instructions from asus.
Doing that should definitely clear what is causing the problem.
Justatechie said:
Im still fine after 10 days of operation. Keep in mind im really using a padfone x that is converted.
What ever it is you should do the downgrade then upgrade again. It shouldn't hurt anything. Just follow the instructions from asus.
Doing that should definitely clear what is causing the problem.
Click to expand...
Click to collapse
i do exactly what asus said. i started from kitkat .17, factory reset, upgrade it to kitkat .18, factory reset, upgrade to lollipop, factory reset again, installing all apps i needed. working fine for a week before it gave me BSOD. so i tried to reinstall the lollipop again after i did factory reset. but it was getting worse, i got BSOD even before installing any apps.
now i am back to .18 kitkat. maybe i ll just wait for next lollipop. thanks.
highbud said:
i do exactly what asus said. i started from kitkat .17, factory reset, upgrade it to kitkat .18, factory reset, upgrade to lollipop, factory reset again, installing all apps i needed. working fine for a week before it gave me BSOD. so i tried to reinstall the lollipop again after i did factory reset. but it was getting worse, i got BSOD even before installing any apps.
now i am back to .18 kitkat. maybe i ll just wait for next lollipop. thanks.
Click to expand...
Click to collapse
Do you have a link for this old ROM in case I need it also later down the line?
Not that I want to go back to whatever happened with the old Padfone X rom from AT&T (or Padfone S one), but I somehow think that having Root is what caused me to have problems to begin with. I haven't done root on this one yet so if I'm not having problems (and have full SD card access with Lollipop), then I'm probably not going to... :/
Lauren
alissa914 said:
Do you have a link for this old ROM in case I need it also later down the line?
Not that I want to go back to whatever happened with the old Padfone X rom from AT&T (or Padfone S one), but I somehow think that having Root is what caused me to have problems to begin with. I haven't done root on this one yet so if I'm not having problems (and have full SD card access with Lollipop), then I'm probably not going to... :/
Lauren
Click to expand...
Click to collapse
mine is padfone s, just look for ww .18 for manual downgrade (manually through stock recovery) or ww .99 in case for automatic downgrade. it's basically the same kitkat.
http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+S&p=29&s=1
if you want to downgrade automatically you must use .99 because the phone can only detect new firmware only when the version number is bigger then current one i think.
blambo said:
XPOSED works just fine on this updated ROM.. Lots of Lollipop whistles and bells work with the activated modules. (You must be rooted of course.)
Click to expand...
Click to collapse
Which XPOSED installer did you use for Lollipop on Asus Padfone S? I just tried one for Lollipop and I got stuck at the boot logo (not a bootloop, just hung).
TigerC10 said:
Which XPOSED installer did you use for Lollipop on Asus Padfone S? I just tried one for Lollipop and I got stuck at the boot logo (not a bootloop, just hung).
Click to expand...
Click to collapse
I had the same issue as well with both XPOSED and SuperSU. Kingroot worked fine though for rooting for me.
I've just tried flashing this both by rebooting with the file in the root of the internal sdcard and with CWM and both are failing. The error I'm getting in cwm is "This package is for "ASUS_T00N" devices; this is a "t00n".
Does anyone know what I might need to edit in order to be able to flash this? I've got a Padfone S Plus.
Thanks in advance
fmflex said:
I've just tried flashing this both by rebooting with the file in the root of the internal sdcard and with CWM and both are failing. The error I'm getting in cwm is "This package is for "ASUS_T00N" devices; this is a "t00n".
Does anyone know what I might need to edit in order to be able to flash this? I've got a Padfone S Plus.
Thanks in advance
Click to expand...
Click to collapse
Open the zip file, don't extract then go to META_INF/com/google/android then open updater-script with a text editor, most people suggest using a unix based text editor such as Notepad++, but I have found that wordpad works fine, delete the entire first line. Save, then retry install. If that doesn't work, use adb sideload.
Delete line in bold text in example below:
Code:
[B]getprop("ro.product.device") == "ASUS_T00N" || abort("This package is for \"ASUS_T00N\" devices; this is a \"" + getprop("ro.product.device") + "\".");[/B]
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
ui_print("installing rpm");
package_extract_s_file("firmware-update/rpm.mbn", "/dev/block/platform/msm_sdcc.1/by-name/rpm");
ui_print("installing sbl1");
package_extract_s_file("firmware-update/sbl1.mbn", "/dev/block/platform/msm_sdcc.1/by-name/sbl1");
ui_print("installing aboot");
package_extract_s_file("firmware-update/emmc_appsboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/aboot");
ui_print("installing tz");
package_extract_s_file("firmware-update/tz.mbn", "/dev/block/platform/msm_sdcc.1/by-name/tz");
), "");
ifelse(msm.boot_update("backup"), (
ui_print("installing rpmbak");
package_extract_s_file("firmware-update/rpm.mbn", "/dev/block/platform/msm_sdcc.1/by-name/rpmbak");
ui_print("installing sbl1bak");
package_extract_s_file("firmware-update/sbl1.mbn", "/dev/block/platform/msm_sdcc.1/by-name/sbl1bak");
ui_print("installing abootbak");
package_extract_s_file("firmware-update/emmc_appsboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/abootbak");
ui_print("installing tzbak");
package_extract_s_file("firmware-update/tz.mbn", "/dev/block/platform/msm_sdcc.1/by-name/tzbak");
),"no backup partition");
msm.boot_update("finalize");
ui_print("installing DDR");
package_extract_file("firmware-update/DDR.img", "/dev/block/platform/msm_sdcc.1/by-name/DDR");
ui_print("installing modem");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
ui_print("installing asusfw");
package_extract_file("firmware-update/asusfw.img", "/dev/block/platform/msm_sdcc.1/by-name/asusfw");
Thanks a heap Daggorlad, that worked a treat.
Would you know how I can load either twrp or cmw back on using terminal emulator? It throws me a "Unknown username or uid" error though it worked under kitkat.
su -c 'dd if=/sdcard/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
Shoot me over some pp details and I'll buy you a beer.
fmflex said:
Thanks a heap Daggorlad, that worked a treat.
Would you know how I can load either twrp or cmw back on using terminal emulator? It throws me a "Unknown username or uid" error though it worked under kitkat.
su -c 'dd if=/sdcard/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
Shoot me over some pp details and I'll buy you a beer.
Click to expand...
Click to collapse
I'm sorry, but I haven't installed using terminal emulator, I have only ever used fastboot to install recovery on this device.
1. Drop the recovery.img in the same directory as fastboot.exe on your PC..
2. Open CMD and navigate to directory where fastboot.exe and recovery image are located. (can also CTRL+Shift+left click on the folder in which they are located and select Open command window here)
3. Reboot phone into fastboot mode by powering off and holding volume up while powering on or using adb reboot bootloader
4. Run:
Code:
fastboot install recovery [I]recoveryname[/I].img
fastboot reboot
I hope this helps and no need for a beer, just helping others like I have been helped here :good:
Thanks Daggorlad, my command prompt just sits at " < waiting for device > "
I powered up the phone holding down the Vol up and it sits on the ASUS screen. Is there anything else I need to get fastboot to work?
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
neocortex08 said:
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Click to expand...
Click to collapse
He is correct. You have to be on CM. EMUI will NOT allow closed to work. Flash the uninstaller zip.
icyboyice said:
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
Click to expand...
Click to collapse
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
neocortex08 said:
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
Click to expand...
Click to collapse
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Moody66 said:
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Click to expand...
Click to collapse
Thanks! As excited as I am to have Xposed, I really like my EMUI (and don't want to pay for the play store one you suggested to others), I like B321s stability, and I like not changing settings often. So for now I'll wait and deal with not having trivialities like AdAway or playing Youtube in the background.
@neocortex08
You only need root on your phone to be able to install adaway. You don't need xposed.
For background playback of YouTube videos you may want to check this out
http://forum.xda-developers.com/showthread.php?t=2213945
They have a install method for those who are rooted and have xposed and those who don't .
Hi to everyone here... Finally a MoKee ROM is relased for Xiaomi Mi 9 SE (grus) devices!
Developer: subdragonzj
This thread will be unofficial for testing of a AOSP-MoKee ROM builded from the source...
(and ROM based on MoKee with some mods builded by myself)
Stay tuned
I have to say that I was pleasantly surprised by this ROM. It doesn't have the existential issues of PE, so it has all those little useful features out of the box (instant face unlock, double tap to sleep on the lockscreen, etc.). It's not XenonHD based, so no freezing incoming calls. Performance is good (closer to xiaomi.eu). Fingerprint scanner is reasonably fast (I say reasonably because xiaomi.eu is always two steps ahead, in this department). And battery life is also optimized to best levels.
I had issues completing Google setup and with wifi, but I have to be honest: I installed the ROM on top of the latest xiaomi.eu (without sound issues, by the way). Now I have 10.3.4 eea vendor. Let's see how it performs on everyday tasks.
PS - Also, I didn't like the ads on MoKee Center, but Adway takes care of that, of course. I have several paid apps from Play Store, so if the ROM is really good, I have no problems with donation for some extra features.
Can you tell us which steps you made to install mokee properly?
Cheers
Gesendet von meinem MI 9 SE mit Tapatalk
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
elpaablo said:
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
Click to expand...
Click to collapse
Ultra-wide camera is broken due to missing some nodes at the kernel dtsi on Xiaomi side (their kernel source is too much broken stuff, even for MIUI itself, which is funny).
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.[/QUOTE]
does it support camera 2 API full
I'm using this ROM for now because it's more optimized than PE. Apart from color profiles that don't stick in any AOSP ROM and a dark theme with white notifications, everything else (except camera, as posted above) is working fine. Fingerprint scanner is reliable (although still a little slow), face unlock is instant and the only issue that needs to be solved asap is ultra wide lens not working. A custom kernel can deal with that, but the stock kernel performs better with this ROM. So, I think I'll wait for a fix or other ROM development.
Anyone getting this on any of your AOSP ROMs?
Been using for 3 days now, and by far it gives the ideal battery performance. Tried crDroid and although there were some improvements, couldn't last a day with barely 20% and high idle drain.
Will be staying with this ROM as everything that I expect from this device is provided for. Personally, no battery means no phone for me, so that's my baseline. Thanks to the other developers for their hard work and free time!
elpaablo said:
Anyone getting this on any of your AOSP ROMs?
Click to expand...
Click to collapse
For now, custom AOSP ROM have 177k-184k antutu score, and it's normal.
you can't expect it to be as close as miui (which can go between 185k-195k).
besides, antutu doesn't represent the true performance since anyone can hack it just like huawei before.
btw, this is from some unreleased custom rom that I use right now, no kernel mod, no nothing. typical custom aosp's score
Yes, but generally it gives you the right idea. The ROM is very fluid. I've installed all my stuff and it remains fluid. In fact, I think the latest nightly update has improved user experience.
Then comes maintenance and that's what worries me the most. We see ROMs (XenonHD and PE) that freeze on incoming calls. This is not just a little bug, it's a massive bug. It basically disables your phone. And it's not been solved yet? crDroid developer seems to think that SIM management is not important in a dual SIM phone. Instead, he tries to make fingerprint scanner work 0.1 seconds faster. Yes, camera is not fully working on MoKee and I really hope that this issue is solved, but at least I can receive calls and enable my data SIM card only when I use it, which saves a lot of battery.
---------- Post added at 05:57 AM ---------- Previous post was at 05:36 AM ----------
I installed latest xiaomi.eu version last week and it's way ahead in every aspect, except 2: MIUI (sucks) and SIM management. AOSP ROMs (except crDroid) handle SIM management in a much better (easier) way.
elpaablo said:
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Click to expand...
Click to collapse
Sorry for picking this up again, i´d like to give mokee a try.
which faceunlock.zip did you use?
https://forum.xda-developers.com/android/software-hacking/mod-fix-gapps-unlock-t3863509 The one from this thread?
Thank you, Cheers.
Sooo now i´m stuck on fastboot.
Tried flashing vbmeta using fastboot with "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", but it just says "fastboot.exe: unknown option -- disable-verity"
Any ideas?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It's the exact phrase I copy/paste.
Maybe you added a space somewhere?
If you're using power shell type cmd first.
Face unlock: https://androidfilehost.com/?fid=11410963190603910002
i used copy/paste too.. i´ve attached a screenshot.
That´s really annyoing atm..
Type cmd or just use cmd instead of PowerShell.
Yes you should always use cmd in administrator mode in the same folder than vbmeta.img
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Humpfrey said:
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Click to expand...
Click to collapse
Can you tell us where is located fastboot and vbmeta.img on your pc?
For instance, i have all my files in c:\Android
So I launch the cmd directly in that folder.
Started by DL https://androidfilehost.com/?fid=962187416754459552
Copied on C drive and renamed into Android
Then I copy my files on it, and right click/launch as admin on "cmd-here".
So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
Code:
fastboot boot twrp-3.3.1-0-tucana-mauronofrio.img
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the
Code:
OrangeFox-Unofficial-tucana-20191120.zip
file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Thanks for taking the time to order it, good job
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
DeathByArmadillo said:
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
Click to expand...
Click to collapse
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
h8Aramex said:
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
Click to expand...
Click to collapse
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
DeathByArmadillo said:
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
Click to expand...
Click to collapse
Yea I tried to find blobs today for 730g but there is nothing on the internet (yet?).
I mean, the phone works for me - if they just fix the missing "Ignore Do Not Disturb" option, I am golden...
flashed orangefox through twrp, touch doesnt work at all. But it worked on the first time, flashed MIROOM. Maybe it is related to the currently installed rom.
Edit: Flashed TWRP from fastboot and touch is working again. Just to be sure, reflashed orangefox and it didn't work again... I'll stick to TWRP, although I dont know if it is a problem with TWRP but i can't flash GSI roms
Hello,
Sorry for my Bad english.
with the stable rom 11.0.7, the orange fox touch works perfectly.
but with development roms, touch does not work. tested with 20.1.9 and 20.1.15.
Touch work with flashed twrp from fastboot
h8Aramex said:
So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Click to expand...
Click to collapse
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
ronademe said:
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
Click to expand...
Click to collapse
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
h8Aramex said:
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
Click to expand...
Click to collapse
Don't worry bro my english is good enough to unserstand the guide ?...but i need to know for exemple words or expressions liké" boot to recovery" etc... How to do that ? What touches to use on Windows
You know what i mean ? I need images or pictures step by step if possible ?????
Can we just install Global Rom in the update option under settings ?
I mean, without needing to unlock the bootloader ?
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Checking for updates
how long does it take to cheking for updates i stuck ? Thank you.
anyone with this rom experiencing huge battery drain ?
sigma119 said:
anyone with this rom experiencing huge battery drain ?
Click to expand...
Click to collapse
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
H-Emmanuel said:
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Click to expand...
Click to collapse
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
There is a MIUI Global 11.0.13? The latest I see is 1.0.7?
I'm looking to update for improved camera speed etc.
First timer on Global Rom, now o EU Beta. Followed instructions, nothing else needed. Thanks a lot! (also, having an usb mouse just in case paid off)
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
sigma119 said:
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
Click to expand...
Click to collapse
Well, that's better than battery drain I hope android 10 with miui will be flawless:fingers-crossed:
About This Rom
This is a debloated stock rom based on stock F800K_30H. Most likely the last update the V20 will get.
Installation Procedure for F800 L/K/S
Download the F800***.7z to a PC and extract with 7-zip app on Windows PC or the equivalent on OSX / Linux . This will expand to a single 6GB system.img file. Copy over to internal storage on your device.
Update TRWP recovery to 3.4.x.x using TWRP.
Download also the F800 boot imgage and F800K-ezv2020.zip kernel.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Boot into twrp and flash the system image.
Install>Install_Image(bottom right)>navigate to system.img file and select system image partition.
Repeat the same procedure for the boot.img, flash on boot partition.
Flash ezV2020 Kernel and then Magisk. Done.
If you are coming from Oreo download also the Pie partitions and flash that first, then as above. Also wipe data so have your apps backed up.
In the case your were already on PIE no need to wipe data but do wipe Dalvik / ART cache and Cache in TWRP before reboot. Device will be slow for a while and will speed up as Dalvik cache is rebuilt in the background. Sometimes that can take a while especially if you don't let the device rest.
==========================================================
Update Nov 2022: You now need to flash in twrp this Chrome update to pass initial setup screen after phone reset or fresh flash.
F800 - Google Drive
drive.google.com
Release v2
This is based on K rather than L for no good reason (new: flash the K partitions in my repo and ezv2020 K kernel), but makes no difference as all carrier apps have been deleted. This is a 'start again' version rather than an update to ver 1 and is recommended to update due to reports of better performance.
Added
QLens
V30 and G6 themes ( I like the black one with dark grey accents)
Sim unlock app (I think it's for phones locked to sim, not sure if it is or if it works)
Wap Push Service (for carrier settings sent via text msg)
Collage Wallpapers from G6 - only works on Lock Screen, dunno why, i'll try fix.
LG Smart World. You must hide it in Magisk first, then software update. Don't know how to change Korean language, sorry.
If you don't care for any of these additions delete them from /system/product/app , using a root browser
RCT (root check tool) remover has already been applied.
Known issues (minor)
Touch screen is not responsive after coming out of Laf Download Mode at times. To recover this simply reboot into recovery and reboot. It's not that serious and doesn't occur after a normal reboot. You just need to be aware of the fix in case you experience it.
If you have any apn issues do the 'reset apn settings to default' in the apn settings menu. Cuz my carrier apn didn't show up initially.
==========================================================
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
TarAntonio said:
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
Click to expand...
Click to collapse
Install Mixploer from here http://mixplorer.com/
Download the attachment provided and extract the folder to Internal Storage
Using Mixplorer copy and paste the Folder named LGCalendarProvider to...
root>system>product>priv-app
(you may be asked to grant root permission here)
Make sure you can see the LGCalendarProvider Folder is in priv-app folder, now reboot.
Google calendar is working for me now.
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
TheRoyalDuke said:
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
Click to expand...
Click to collapse
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
ezzony said:
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
Click to expand...
Click to collapse
Bluetooth works fantanstic. Connected my portable speaker and it played smoothly, never disconnected.
TheRoyalDuke said:
Edit: F800L30H_Partitions is needed to get fingerprint working.
Click to expand...
Click to collapse
Thanks for that. It might be just the modem that is needed. Can you get into download mode after flashing the partitions? Be careful. That is why I said in the OP don't flash Pie Partitions on non-F800 although you may not have seen that as I added it later.
I have a zip somewhere to flash back oreo partitions. I'll upload it later.
edit: just checked my us996, fingerprint is working fine without flashing pie partitions. Please delete your edit as I don't want anyone flashing pie partitions on non-f800 devices because of the laf download problem.
I will have to figure out what exactly is going on but until then I don't support of advise anyone to flash Pie partitions on any non-F800 device.
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
TheRoyalDuke said:
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
Click to expand...
Click to collapse
Ah good. Because there was an issue with the new Pie LG LAF (download mode) not being detected in LGUP. Experienced that myself. The danger is then if you accidentally deleted TWRP or somehow got corrupted there would be no way to ever flash the phone again and you'd be stuck with what you have. That is why I'm being extra cautions.
Note:
I still don't advise anyone to flash pie partitions on non-f800. There are so many variants it's not certain or knowable if all will be okay for all of them.
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloated right?
xxseva44 said:
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloat right?
Click to expand...
Click to collapse
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
ezzony said:
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
Click to expand...
Click to collapse
Ahh okay, thx for letting me know
Edit: So i flashed it and at first it was very stable but then it crashed to that green apps watchdog bark, i then rebooted and it crashed and showed the purple secure watchdog bite screen a couple of seconds after unlocking the phone. not sure if this is relevant but when it crashed it was downloading about 40 apps, and i was trying to log into instagram. Maybe it was just a fluke, i'll see if it happens again
Edit2: So i rebooted and everything seems fine again
Edit3: okay so it crahsed again, same thing happened, it crashed to the green watchdog bark screen although this time it went from that screen to the purple watchdog bite screen without rebooting or anything. When it crashed, i went to unlock it and it froze while i was unlocking the phone
Could this have anything to do with the fact that my phone was originally a vs995? Cuz i converted it to a us996, I noticed that there was a vs995 pie kernel, should i flash that and see if the crashes stop? I'm not too sure if it would do anything especially since i was running alpha omega oreo with your us996 oreo kernel just fine but it's worth a shot but just to be sure, for now i'll reflash the us996 kernel again and see if the crashes return
update: It worked fine for the past hour but crashed to the watchdog bite screen again, i'll try flashing the vs995 pie kernel and see if the crashes stop. Okay so i successfully flashed it, now i just have to wait and see
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
xxseva44 said:
Ahh okay, thx for letting me know
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Click to expand...
Click to collapse
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
ezzony said:
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
Click to expand...
Click to collapse
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
TheRoyalDuke said:
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
Click to expand...
Click to collapse
You could try flashing the modem only. The pie modem, in twrp. I'd be curious to know what would happen. I have just uploaded it. Worth a try. The fingerprint for some reason uses files in the modem partition. Why there are there I don't know.
Be advised everyone all this mixing and matching pie with oreo may result in unforeseeable negatives. We can only know what works by trial and error. And, your welcome!
xxseva44 said:
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
Click to expand...
Click to collapse
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
ezzony said:
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
Click to expand...
Click to collapse
Yea i double checked, i flashed the us996 pie kernel twice actually, but had the same results
Okay so before i added anything, i tried to open the alexa app again, this time it worked fine and didn't cause my phone to crash, so this time i'm going to open a lot of apps and see if that will trigger the crash
Edit: nope, that did not cause it to crash either, i have no idea what's causing the crashes, maybe it has something to do with the cache because i remember when i tried rebooting after the second crash, it was stuck at the boot animation, it only rebooted after i cleared delvik and cache. Maybe the cache is getting corrupted after a while?
Update: Phone has been running fine for 1 day
Update2: Phone crashed this morning while scrolling to instagram, these crashes seem to be happening at random. Only thing the crashes have in common is that it would happen roughly every 20 hours to a day. Sometimes if i'm unlucky it just repeatedly crashes after a couple of reboots
Update3: Okay yea theres something funny going on with the cache because, i went to the gallery to look at some videos that i know would play but when i tried to play them it kept saying something went wrong, tried a reboot but still the same result. and when i'd watch videos on instagram they looked corrupted, tried force stopping and clearing the cache but still the same result. reboot didn't help either, only thing that fixed those issues was clearing the cache and delvik in twrp
Update: So i have found a temporary solution which is to clear the cache and delvik every once in a while
Idk if this is relevant but what did you come from before flashing this cuz i came from oreo so idk if that could have anything to do with the issue