I just purchased Mi Pad 4 and MIUI 9.6 is pre installed. Current ARB level is 1. Should I upgrade it to MIUI 10.1 or should I keep it with MIUI 9.6?
Thanks
Just got mine 2 days ago as well. Upgraded to 10.1 and did not spot any issues. However, I am not sure why the location does not work in Google Maps yet... I get a notification that it is searching for the GPS, but nothing happens. I have the LTE 64 GB version.
greentrancer said:
Just got mine 2 days ago as well. Upgraded to 10.1 and did not spot any issues. However, I am not sure why the location does not work in Google Maps yet... I get a notification that it is searching for the GPS, but nothing happens. I have the LTE 64 GB version.
Click to expand...
Click to collapse
Mi pad 4 doesnt have gps as far as i know. Only plus model has it
My Mi Pad 4 has 9.6.26.0 Chinese stock ROM which has only English and Chinese languages. Current ARB level is 1. If I upgrade it with OTA to MIUI 10.1.1.0, what will be ARB level? What are the differences between MIUI 9.6.26 and 10.1.1?
Incogn said:
Mi pad 4 doesnt have gps as far as i know. Only plus model has it
Click to expand...
Click to collapse
I do not know about the Plus, but the simple Mi Pad 4 with LTE has! I was able to get it working outside the flat; I guess that the signal in the flat was too weak, even though that my OnePlus 3T works fine...
coolman7 said:
My Mi Pad 4 has 9.6.26.0 Chinese stock ROM which has only English and Chinese languages. Current ARB level is 1. If I upgrade it with OTA to MIUI 10.1.1.0, what will be ARB level? What are the differences between MIUI 9.6.26 and 10.1.1?
Click to expand...
Click to collapse
Why is ARB so important and how can I see it? The differences between the 9 and 10 is in interface, especially the notifications, etc. I did not use 9 a lot, so I do not know what functionality improvements or bugs they added, if any.
greentrancer said:
I do not know about the Plus, but the simple Mi Pad 4 with LTE has! I was able to get it working outside the flat; I guess that the signal in the flat was too weak, even though that my OnePlus 3T works fine...
Why is ARB so important and how can I see it? The differences between the 9 and 10 is in interface, especially the notifications, etc. I did not use 9 a lot, so I do not know what functionality improvements or bugs they added, if any.
Click to expand...
Click to collapse
I can't downgrade if ARB level is higher than 1. If I upgrade it to MIUI 10 and if I don't like it or there are some problems, I can't downgrade it to MIUI 9. Or if I try to downgrade it will brick Mi Pad 4.
You can check ARB level with this command at fastboot:
fastboot getvar anti
Thanks
mi pad 4 has gps. i'm using it right now. but if u have china rom installed, than it will cause problem, with gps outside of china. its a known china rom issue with many xiaomi devices. my device had china stable rom before and i had similar issues. i switched to xiaomi.eu rom and my gps is working perfectly now. im using mi pad 4 8 inch with LTE, not mi pad plus.
only the lte version either 8 inch or plus, has gps afaik
Farhadul Haque said:
mi pad 4 has gps. i'm using it right now. but if u have china rom installed, than it will cause problem, with gps outside of china. its a known china rom issue with many xiaomi devices. my device had china stable rom before and i had similar issues. i switched to xiaomi.eu rom and my gps is working perfectly now. im using mi pad 4 8 inch with LTE, not mi pad plus.
Click to expand...
Click to collapse
Only the LTE versions have GPS.
*edit*
****, beaten.
Well I can't install twrp on mi pad 4 to even upgrade my pad. Everything is unlocked. Every time I go to install twrp IMG it just keeps coming up with error unable to load recovery.img file. It's doing my head in. I've been at it for about 7 hours now. I give up.
Well I can't install twrp on mi pad 4 to even upgrade my pad. Everything is unlocked. Every time I go to install twrp IMG it just keeps coming up with error unable to load recovery.img file. It's doing my head in. I've been at it for about 7 hours now. I give up.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
I'm running MIUI 9.6.27.00 stable. It's just not letting me install it. I changed the name of the twrp IMG to recovery.img still not letting me install.
bigall123 said:
Well I can't install twrp on mi pad 4 to even upgrade my pad. Everything is unlocked. Every time I go to install twrp IMG it just keeps coming up with error unable to load recovery.img file. It's doing my head in. I've been at it for about 7 hours now. I give up.
Click to expand...
Click to collapse
You don't need to flash TWRP. You can just boot TWRP from fastboot by this command:
Code:
fastboot boot TWRP.img
TWRP Install.
This is what im getting. im about to give it up as a bad job. C:\WINDOWS\system32>fastboot boot TWRP.img
cannot load 'TWRP.img': No such file or directory
C:\WINDOWS\system32> Thanks anyway.
bigall123 said:
This is what im getting. im about to give it up as a bad job. C:\WINDOWS\system32>fastboot boot TWRP.img
cannot load 'TWRP.img': No such file or directory
C:\WINDOWS\system32> Thanks anyway.
Click to expand...
Click to collapse
You should replace TWRP.img with your recovery image file that you downloaded from internet.
Do you no when I'm in the command prompt window. Do you no when you type in a command, do you star every command with ADB then the command. For instance, ADB fastboot boot twrp.img. thanks. When I try & type a command with out the ADB at the start it comes up with IMG not found. Thank. Can you provide the link to the image that I need. I have also tried the install flash tool but no joy.
bigall123 said:
Do you no when I'm in the command prompt window. Do you no when you type in a command, do you star every command with ADB then the command. For instance, ADB fastboot boot twrp.img. thanks. When I try & type a command with out the ADB at the start it comes up with IMG not found. Thank. Can you provide the link to the image that I need. I have also tried the install flash tool but no joy.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-pad-4/how-to/offical-mokee-twrp-t3884087
MIUI 10.2.1 released. Anyone can check anti roll back level with this command?
Code:
fastboot getvar anti
Thanks
Related
Hi guys, so my new Redmi Note 3 Pro (3GB Ram/ 32Gb rom) came in the mail today. I was excited because I want to give this phone to my father and I know its a good phone since I have one myself, running CM13. However, my problem is that I am unable to access EDL mode . I did adb command to run "adb reboot edl" and it just restarted the phone. I even did the volume combination keys and I am still unable to access EDL mode. I went the extra mile to even unlock the bootloader officially so it should be at a good start right now as it is. I suddenly realized that I might have a vendor rom running on my new Redmi Note 3 Pro. I looked up everywhere on google and none of the tutorials help me get rid of the vendor rom to flash back to official rom. Many of the threads from MIUI havent helped me. I was hoping if anyone could help me revert back to stock MIUI, doesn't matter which (developer, stable, china developer, etc.) I have took some screenshots from the phone to show you what vendor rom I am currently running and plus some of the errors I have came across while trying to go back to stock MIUI. I have done the whole flashing and unlocking bootloader before so i know the process and im not afraid to take instructions. Any help guys, I would really appreciate it!
Edit: Yes, i have also disabled my signature drivers while doing all of this.
did you try this method. forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
V-incent said:
did you try this method. forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Click to expand...
Click to collapse
I have. It is like as if the phone came with no EDL partition or something. I don't think that's possible. But yes I have tried that method, it was fastboot v2. Not sure what version that one is but I believe they operated the same way.
I'm open to the idea of rooting the phone with this pre-installed Vendor Rom and from there I can wipe it and flash CM13 since my bootloader is already unlocked. However I'm not sure if there a case for rooting and installing TWRP on vendor roms for Redmi note 3
Transfer latest global rom on the phone and use updater to flash?
HParra97 said:
I'm open to the idea of rooting the phone with this pre-installed Vendor Rom and from there I can wipe it and flash CM13 since my bootloader is already unlocked. However I'm not sure if there a case for rooting and installing TWRP on vendor roms for Redmi note 3
Click to expand...
Click to collapse
I can try help you. Please, send me PM
privateriem said:
Transfer latest global rom on the phone and use updater to flash?
Click to expand...
Click to collapse
Yeah I've tried that /: apparently those who have a fake Rom (Vendor Rom) cannot update via OTA by the updater app
Its not adb reboot edl.
Search n download fastboot reboot edl zip in miui forum.
Reboot edl will work from fastboot.
You do not have the Snapdragon Redmi Note 3. You have the Mediatek version as evident from your screenshot saying the processor type as "Octa-Core". The EDL mode does not work on Mediatek devices, as far as I know. You can follow this guide for MediaTek devices.
It's the non-pro version with mediatek chipset
You have been fooled
ayush3051 said:
You do not have the Snapdragon Redmi Note 3. You have the Mediatek version as evident from your screenshot saying the processor type as "Octa-Core". The EDL mode does not work on Mediatek devices, as far as I know. You can follow this guide for MediaTek devices.
Click to expand...
Click to collapse
nguyenlucky said:
It's the non-pro version with mediatek chipset
You have been fooled
Click to expand...
Click to collapse
I see. Thanks guys for helping me notice that.
Hey there!
I'm using the Redmi Note 3 Pro for a few months now with CM. Since CM is a bit buggy for me and I would love to try out the new MIUI 8, most preferred the official global release.
But unfortunately I'm struggling, nearly fighting , with my device for a few days now. Problem is that I can't get anything to work properly on my device.
Here is what I did (Phone is of course offically unlocked) :
Downloaded the latest MIUI 8 global from the official site. First mistake was to take the wrong version. I allways thought that my device is a kenzo. But it's a kate. OK, so I tried to use the global version for the special edition. When I flash the zip via TWRP everything seems to go normal but in the end the process stops at "package_extract_file took 00s". I let the flash process run over night, so there is definitely a freeze at that point. This step stayed for over 8 hours.
Strange thing here is that the process looks exactly the same, regardless what image (kenzo or kate) I choose.
After the TWRP attempt I tried to flash the fastboot image via MiFlash. Here is the problem a different one: MiFlash won't allow kenzo images. So far so good. But when I take the kate fastboot image the process fails when flashing system.img (file too large). I found out that using a custom rom like CM changes the system-partition size (system1 and system2 merged to system?) for more space. But I don't know how to fix that.
Now I'm pretty clueless and not sure what to do. Is there a way to get MIUI running or am I forced to use CM? What can I do? I am very thankful for every hint or advice you can give me. Thank you!
Have u ever tried using edl mode ?
No, edl mode is new to me.
Try flashing the Fastboot ROM uisng Mi Flash Tools with your phone in EDL Mode.
See this.
http://xiaomitips.com/guide/how-to-put-redmi-note-3-into-edl-mode/
Yeh Use edl ....you'll be fine
THANK YOU VERY MUCH EVERYONE
EDL worked like a charm. Should have asked earlier
Thanks guy!
So now that the K20 Pro subforum is open, I'd like to make a post here to quickly sum up what we have right now before any device-specific AOSP development has started.
LR.Team/wzsx150's TWRP
Original thread: http://www.miui.com/thread-24561276-1-1.html
Mirrored here: https://drive.google.com/open?id=1miIo5BZqgEHh0t5PyjwFkFryosLuFOXk
Usage: unlock BL, flash recovery image to recovery and misc.bin to misc via fastboot
Status on GSIs
PHH wiki page: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-K20-Pro
TL;DR: the biggest issue is the pop-up camera, but that has been partially resolved by PHH (manual controls); other bugs are either generic to GSIs or not deal-breakers. I myself have been using my own LOS GSI for a week by now and I'd say it's good for daily driver, and certainly good enough as an intermediate stop before actual ROMs happen. Once the overlay I submitted is merged, all GSIs built afterwards should be on equal footing. I'll also keep eyes on the issues page in case PHH needs anything for another fix.
And finally, here's a script I made for users who want to use unencrypted storage - format /data and flash this. This one was actually made for Mix 2, but also works here, while Zackptg's universal script doesn't seem to work.
AndyYan said:
So now that the K20 Pro subforum is open, I'd like to make a post here to quickly sum up what we have right now before any device-specific AOSP development has started.
LR.Team/wzsx150's TWRP
Original thread: http://www.miui.com/thread-24561276-1-1.html
Mirrored here: https://drive.google.com/open?id=1miIo5BZqgEHh0t5PyjwFkFryosLuFOXk
Usage: unlock BL, flash recovery image to recovery and misc.bin to misc via fastboot
Status on GSIs
PHH wiki page: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-K20-Pro
TL;DR: the biggest issue is the pop-up camera, but that has been partially resolved by PHH (manual controls); other bugs are either generic to GSIs or not deal-breakers. I myself have been using my own LOS GSI for a week by now and I'd say it's good for daily driver, and certainly good enough as an intermediate stop before actual ROMs happen. Once the overlay I submitted is merged, all GSIs built afterwards should be on equal footing. I'll also keep eyes on the issues page in case PHH needs anything for another fix.
And finally, here's a script I made for users who want to use unencrypted storage - format /data and flash this. This one was actually made for Mix 2, but also works here, while Zackptg's universal script doesn't seem to work.
Click to expand...
Click to collapse
OMG! Thank you so much in advance! ???
---------- Post added at 06:47 PM ---------- Previous post was at 06:08 PM ----------
I'd love to see a more detailed "noob friendly" guide on how I can get this twrp working on my K20 Pro. Hope one will be available in YouTube soon.
melmarPH said:
I'd love to see a more detailed "noob friendly" guide on how I can get this twrp working on my K20 Pro. Hope one will be available in YouTube soon.
Click to expand...
Click to collapse
Uhh... What difficulty do you have with simply flashing TWRP? I believe that doesn't need a guide.
Thanks for your work with PHH on getting a usable GSI image. Do you have a PD charger? I was wondering if you still get 27W charging via PD?
I'll be ordering this in the next day or 2, now the prices have come down to a sensible level on AliExpress. Hopefully by the time it arrives and I get to unlock the bootloader a few more issues will have been resolved thanks to the now released kernel sources.
Thanks a lot bro!!!!!
how do you flash the misc using fastboot? and is this english language?
narugan26 said:
how do you flash the misc using fastboot? and is this english language?
Click to expand...
Click to collapse
fastboot flash misc misc.bin
Chinese default, and you can change to English in setting via same step as other official TWRPs.
AndyYan said:
Uhh... What difficulty do you have with simply flashing TWRP? I believe that doesn't need a guide.
Click to expand...
Click to collapse
Please correct me if im wrong..
1. Unlock bootloader
2. Fastboot flash recovery twrp.img
3. Fastboot flash misc misc.bin
Is that correct?
Robbo.5000 said:
Thanks for your work with PHH on getting a usable GSI image. Do you have a PD charger? I was wondering if you still get 27W charging via PD?
Click to expand...
Click to collapse
I didn't buy the optional 27W charger; stock 18W charger charges the phone at 9V 1.85A (~17W) as measured by a physical USB meter (I don't trust any software readings).
melmarPH said:
Please correct me if im wrong..
1. Unlock bootloader
2. Fastboot flash recovery twrp.img
3. Fastboot flash misc misc.bin
Is that correct?
Click to expand...
Click to collapse
Looks good to me.
Nice to see you here @AndyYan ! Loved your consistent work on the mix2! You bought the k20pro as well?
ugene1980 said:
Nice to see you here @AndyYan ! Loved your consistent work on the mix2! You bought the k20pro as well?
Click to expand...
Click to collapse
Yeah it's my new primary device. I don't plan to do any building/"development" here though, this device should be popular enough to attract more capable devs on its own - that is, after it's released internationally.
May I ask what is the purpose of tha misc.bin?
AndyYan said:
Yeah it's my new primary device. I don't plan to do any building/"development" here though, this device should be popular enough to attract more capable devs on its own - that is, after it's released internationally.
Click to expand...
Click to collapse
Hi Andy, quick question.
Do you think the non-pro version of the phone will receive the same level of custom ROM support as the pro version? If I am not mistaking, the only difference that affects developers is the SD730 instead of the SD855. The reason I am asking is because I dislike MIUI, but (currently) only the Xiaomi Mi 9T is available where I live. I do not mind buying the non-pro version, but I do want much custom ROM support. Do you suggest waiting for the Xiaomi Mi 9T Pro or importing the Redmi K20 Pro over buying the Xiaomi Mi 9T (w.r.t. custom ROM support)?
Krullendhaar said:
Hi Andy, quick question.
Do you think the non-pro version of the phone will receive the same level of custom ROM support as the pro version? If I am not mistaking, the only difference that affects developers is the SD730 instead of the SD855. The reason I am asking is because I dislike MIUI, but (currently) only the Xiaomi Mi 9T is available where I live. I do not mind buying the non-pro version, but I do want much custom ROM support. Do you suggest waiting for the Xiaomi Mi 9T Pro or importing the Redmi K20 Pro over buying the Xiaomi Mi 9T (w.r.t. custom ROM support)?
Click to expand...
Click to collapse
Past "parallel" sub-flagships like Mi 8 SE / Mi 9 SE aren't even close to their flagship counterparts in terms of support, plus SD730 is a chip only used by 2 devices so far. Wouldn't count on it.
Still, given the two's similarity, it should be a cakewalk to get GSI running on it with the same bugs, and if something gets fixed on one, the other should benefit as well.
dmj0shu4 said:
May I ask what is the purpose of tha misc.bin?
Click to expand...
Click to collapse
idk either, but all releases for all devices from wzsx150 include this step, so I figure can't go wrong with just copying his steps.
dmj0shu4 said:
May I ask what is the purpose of tha misc.bin?
Click to expand...
Click to collapse
AndyYan said:
idk either, but all releases for all devices from wzsx150 include this step, so I figure can't go wrong with just copying his steps.
Click to expand...
Click to collapse
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
If there are any mistakes, please point out.
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
AndyYan's GSI works well with few bugs.
The only 2 unsatisfactory things I have discovered are:
This GSI LineageOS don't support to unlock phone via fingerprint when screen is off, I have to press the power button first.
And this GSI only have PWM driver when screen is 31% brightness below, while the MIUI supports all brightness DC ( however, xiaomi claimed that K20Pro have HARDWARE DC screen driver ). I have tried 3rd party apk for simulate DC driver, it works, but completely ruines the optical fingerprint at low brightness due to the screen is so dim that can't lit up the finger for fingerprint camera.
Fortunately, Magisk, Edxposed, GravityBox[P] and other xposed modules work, so I will never return to MIUI.
kumoilain said:
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
Click to expand...
Click to collapse
So that's why... Thanks for the explanation!
I always hold down the key combo right after flashing though, so it wouldn't boot into MIUI anyway, but good to know I don't need to do that anymore at least for this device.
kumoilain said:
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
If there are any mistakes, please point out.
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
AndyYan's GSI works well with few bugs.
The only 2 unsatisfactory things I have discovered are:
This GSI LineageOS don't support to unlock phone via fingerprint when screen is off, I have to press the power button first.
And this GSI only have PWM driver when screen is 31% brightness below, while the MIUI supports all brightness DC ( however, xiaomi claimed that K20Pro have HARDWARE DC screen driver ). I have tried 3rd party apk for simulate DC driver, it works, but completely ruines the optical fingerprint at low brightness due to the screen is so dim that can't lit up the finger for fingerprint camera.
Fortunately, Magisk, Edxposed, GravityBox[P] and other xposed modules work, so I will never return to MIUI.
Click to expand...
Click to collapse
Thank you for your clarification. So for now, there is no way to not flashing misc.bin? Because i do not want to touch this partition whatsoever.
xuananh94 said:
Thank you for your clarification. So for now, there is no way to not flashing misc.bin? Because i do not want to touch this partition whatsoever.
Click to expand...
Click to collapse
kumoilain said:
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
Click to expand...
Click to collapse
You can use the first commad above after "fastboot flash recovery twrp.img". It should work.
I think it's ok to overwrite misc partition because configures in misc is always changed (eg. reboot to system from twrp/ reboot to twrp from system)
kumoilain said:
You can use the first commad above after "fastboot flash recovery twrp.img". It should work.
I think it's ok to overwrite misc partition because configures in misc is always changed (eg. reboot to system from twrp/ reboot to twrp from system)
Click to expand...
Click to collapse
So let me clear what I need to do, please tell me if i am wrong:
- extract the .7z file
- take the .img file (64mb) and flash it via adb normally.
- boot to recovery and install whatever i like
Hello, I'm a noob in modding a phone, but I want to try
Some years ago a friend of mine bought a redmi5plus in China and brought it in Europe; he put on it a global MIUI and registered it with a MI account.
Now he sold me his phone, and correctly disassociated it from his account.
What it would be nice to do is to remove the MIUI global, and put a stock android OS, like android 8.1 (with google apps), because I want to give it to my father, and he's a bit old, he learned the standard android and can't fit with the MIUI one (he still asks "where the hack is the menu button with all my apps?" and similar).
So, a pure OS, no MIUI, no non-google-basic apps.
Since I'm quite a noob (ok, I have a computer science degree but I've never touched a phone), could you please help me on learning how to do this?
(or if there's a guide on how to do that, what are the OS list i can mount on it, no problem, just link me)
edit: specs are:
- model: redmi 5 plus
- android version: 7.1.2 N2G47H
- MIUI version: MIUI global 9.2 | stabile 9.2.6.0(NEGMIEK)
- band base: 953_GEN_PACK-1.129634.1.131253.1
- kernel version: 3.18.31-perf-g439dbb6
Thanks!
First you must unlock the bootloader with waiting
https://en.miui.com/unlock/download_en.html
The unlock tool will tell u how long.
Then u need a recovery like
https://forum.xda-developers.com/re...t/recovery-orangefox-recovery-xiaomi-t4054193
This work for orangefox too
https://www.xda-developers.com/how-to-install-twrp/
After you flash over ADB, you must flash again the orangefox.zip in recovery.
And roms look in the right section
You can find many guides at xda
joke19 said:
First you must unlock the bootloader with waiting
https://en.miui.com/unlock/download_en.html
The unlock tool will tell u how long.
Then u need a recovery like
https://forum.xda-developers.com/re...t/recovery-orangefox-recovery-xiaomi-t4054193
This work for orangefox too
https://www.xda-developers.com/how-to-install-twrp/
After you flash over ADB, you must flash again the orangefox.zip in recovery.
And roms look in the right section
You can find many guides at xda
Click to expand...
Click to collapse
Thanks so much man, at least now I know the right steps to do!
Hope everything will be good, tomorrow I'll try.
p.s.: is it necessary orangefox or just TWRP is enough?
tiec7 said:
Thanks so much man, at least now I know the right steps to do!
Hope everything will be good, tomorrow I'll try.
p.s.: is it necessary orangefox or just TWRP is enough?
Click to expand...
Click to collapse
Is your choice what recovery u use, I like orangefox.
joke19 said:
Is your choice what recovery u use, I like orangefox.
Click to expand...
Click to collapse
ah i see I think I need a lightweight one, because this phone will be used by my father
Do you think it's possible to install a standard android 8.1 ? does it exist as a rom?
tiec7 said:
ah i see I think I need a lightweight one, because this phone will be used by my father
Do you think it's possible to install a standard android 8.1 ? does it exist as a rom?
Click to expand...
Click to collapse
No, but you can make miui that it look like stock with a theme and a customer launcher.
Maybe you can use the Xiaomi eu rom.
Google it. It's nice
Sent from my Mi Note 10 using XDA Labs
joke19 said:
No, but you can make miui that it look like stock with a theme and a customer launcher.
Maybe you can use the Xiaomi eu rom.
Google it. It's nice
Sent from my Mi Note 10 using XDA Labs
Click to expand...
Click to collapse
mmm i had a look but i think i'll try evolutionX ( the one in this post: https://forum.xda-developers.com/redmi-note-5/development/evolution-x-4-4-redmi-5-plus-t4122467 )
is there a small guide on how to do the steps to install it? =)
Until now I just disassociated this phone from the old account (was my friend account who gave this phone to me) and I just looked into developer settings and i saw that is already unlocked (don't exactly know what does it means but is it, if there's some explanation of those things in some guide...)
ok, i tried to install it without success, the phone now goes in black screen and stays there.
I installed TWRP with
fastboot devices
fastboot flash recovery twrp.img
boot twrp.img
this step was ok, if i do it from a command line connecting my phone in fastboot mode to the pc, it starts.
then i went on "install" and installed the zip file
EvolutionX_4.5_vince-10.0-20200714-0943-OFFICIAL.zip
from here
https://forum.xda-developers.com/redmi-note-5/development/evolution-x-4-4-redmi-5-plus-t4122467
after that, i rebooted the redmi 5 plus and boom, black screen after some seconds of "mi" screen.
can anyone help me?
ok, i've managed it: i followed these guides: https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
now, I installed havocOS but I just realized there's no camera app. why? how can i do to have it?
edit: no wifi and no mobile connection!! without any of the roms I tried!
someone has any idea?
duplicate
tiec7 said:
ok, i've managed it: i followed these guides: https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
now, I installed havocOS but I just realized there's no camera app. why? how can i do to have it?
edit: no wifi and no mobile connection!! without any of the roms I tried!
someone has any idea?
Click to expand...
Click to collapse
Flash orangefox, install the last global firmware, reboot to the recovery, format not wipe the data partition, reboot again and then your rom
https://xiaomifirmwareupdater.com/firmware/vince/
Sent from my Mi Note 10 using XDA
joke19 said:
Flash orangefox, install the last global firmware, reboot to the recovery, format not wipe the data partition, reboot again and then your rom
https://xiaomifirmwareupdater.com/firmware/vince/
Sent from my Mi Note 10 using XDA
Click to expand...
Click to collapse
the problem with no SIM and no WIFI was exactly the firmware. I didn't even know a phone had a firmware!!
Thanks!!
Now it works with EvolutionX; absolutely no chance of working with
- crDroid
- MSM Xtended
- coltOS
- resurrection remix
- HavocOS
with all of these it gives me a misterious "error 7" during install. Do you know what is this error?
Ok, i solved.
I was absolutely CERTAIN that the ROM I wanted to install was the one made for my redmi 5 plus,
(filename is Havoc-OS-v3.7-20200726-vince-Official-GApps.zip )
so what i did was
- I went to META-INF\com\google\android inside the zip file with winrar
- unzipped to desktop the updater-script file
- since my phone is TOTALLY EMPTY, i changed those lines:
* removed line
Code:
run_program("/tmp/install/bin/backuptool.sh", "backup", "/dev/block/bootdevice/by-name/system", "ext4");
* removed line
Code:
run_program("/tmp/install/bin/backuptool.sh", "restore", "/dev/block/bootdevice/by-name/system", "ext4");
* then, since I read a lot about that but no one ever posted the result, i tried changing this line
Code:
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
with this line:
Code:
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
and i re-inserted this file draggin and droppin it in the winrar window, where the old file was; DO NOT CHANGE THE NAME OF THE ZIP or it will be thrown an error on the zip name;
- wiped system, dalvik, cache, data (if it gives some errors, reboot and retry; if still errors, i formatted data in ext2 then re-formatted in ext4 )
- installed the modded zip
everything went ok.
I am anyway really disappointed by this community, not a single help in 3 days, just "follow guides". Just thanks to joke19 who at least tried to help me giving me some basic info.
tiec7 said:
Ok, i solved.
I was absolutely CERTAIN that the ROM I wanted to install was the one made for my redmi 5 plus,
(filename is Havoc-OS-v3.7-20200726-vince-Official-GApps.zip )
so what i did was
- I went to META-INF\com\google\android inside the zip file with winrar
- unzipped to desktop the updater-script file
- since my phone is TOTALLY EMPTY, i changed those lines:
* removed line
* removed line
* then, since I read a lot about that but no one ever posted the result, i tried changing this line
with this line:
and i re-inserted this file draggin and droppin it in the winrar window, where the old file was; DO NOT CHANGE THE NAME OF THE ZIP or it will be thrown an error on the zip name;
- wiped system, dalvik, cache, data (if it gives some errors, reboot and retry; if still errors, i formatted data in ext2 then re-formatted in ext4 )
- installed the modded zip
everything went ok.
I am anyway really disappointed by this community, not a single help in 3 days, just "follow guides". Just thanks to joke19 who at least tried to help me giving me some basic info.
Click to expand...
Click to collapse
Me too. Nobody push the thanks button in this thread.
Sent from my Mi Note 10 using XDA Labs
Hello developers,
I bought a Huawei P20 lite a few days ago after verifing, that lineage is possible to install on those phones.
Now, after struggling for 3 days to install lineage, I decided to post here.
First some information about my phone:
Device: Huawei P20 lite dual SIM, 4GB RAM, 64GB internal (ANE-L21, i guess?)
Fastboot Info (I ran those commands when creating this post):
fastboot oem get-build-number: ANE-LX1 9.1.0.257(C432E6R1P7) (from what I understood, ANE-LX1 and ANE-L21 Firmwares are the same?)
fastboot oem get-product-model : ANE-LX1
fastboot getvar version: FALED, Command not allowed
fastboot getvar vendorcountry: HW/EU
When I got the phone, I got my bootloader unlock code first.
I then successfully updated the phone to the newest version (the official Huawei approach, using HiSuite).
After that, I unlocked the bootloader with no problems and flashed TWRP.
I needed to try a few versions to find one that's working as the official ones for that phone kept freezing, I finally found one by Pretorian08 that's working).
Then I formatted to get rid of encryption, did the wipe procedure, cleared the cache, data and system partition and installed the newest lineage build and GAPPS.
After rebooting, the Phone showed me the usual "your device has been unlocked and can't be trusted"- dialog, and tried to boot then.
From here on, nothing happened.
I tried every build I could find, including the most actual one from tonight (lineage-16.0-20201214-nightly-anne-signed.zip).
Some builds would reboot after some time and show the shortened warning message, then boot directly into Recovery.
I totally bricked my phone somewhere on the way (multiple times I think), but could unbrick it by flashing rescue_recovery_kernel, rescue_recovery_ramdisk and rescue_recovery_vendor with appropriate img files extracted from a "Anne-L01 Anne-L21 9.1.0.132(C432E5R1P7T8)" - Firmware and then going back to zero by installing a stockrom via dload and unlocking the bootloader again.
I then tried several other custom Roms, but the outcome is always the same: The phone just freezes with the warning message still visible while trying to boot up, or it boots into TWRP.
ROMs I've tried (I'll write the filenames to provide more info):
- Havoc OS-v3.2-20200215-ARM64AB-GSI.img
- Resurrection Remix ARM64_AB_20191205.img (this is the only custom ROM that will do ANYTHING at all: It will show the Red RessurectionMix Bootlogo, but sadly it won't boot past that point)
- Treble AOSP losq-v224-201017-arm64-bvN.img
With the above 3, installing GAPPS is not possible because "not enough free space in system partition"
- Every possible lineage build for that phone
As stated before, I'm struggling with the phone for 3 days now, so I followed a whole bunch of threads and advices, flashed multiple firmware files using different methods and tried like 7 different TWRP versions. With other words: I did a lot of things, which yould possibly mess up the phone and maybe I did something wrong at some point.
Maybe, I flashed a wrong Firmware while trying to unbrick or something like that. Can you guys help me understand what I'm doing wrong?
I don't like it if people post questions in a forum and then don't share what they figured out, so I'll post 's a little update after 6 days:
Here's a serious advice, if you're considering to buy this phone because there are lineage builds available: forget it.
I mean in most cases it seems to work somehow (from what I read), but from my experience I can say now, that there are phones where it apparently just doesn't work.
I've wasted over one week of my holiday working nonstop on that phone, I've downloaded about 50GB of different firmware files, recoveries, patches and custom Roms and flashed my firmware like 40 times. Best thing I could archieve is an indefinitely looping bootlogo in AOSP, lineage won't even get to that point.
I've tried every lineage build available, i've tried EMUI versions from 9.1.0.0X up to 9.1.0.200 (it is stated multiple times that the .200 will definitely work), no chance. I even tried a rollback to EMUI 8 via Hisuite and using old lineag builds in the end.
The fact that I didn't get any advice in this forum leads me to the conclusion, that no one has an Idea on what the problem is here either.
As I don't feel good with using a phone that still has original google stuff and huawei spy/bloatware installed, the only option that is left to me is just throwing it away and using some old phone. That's sad and a real waste of material and time, as the phone is brand new, but using the stockrom is no option to me. I really don't know what went wrong, I've already successully installed lineage (and cyanogenmod before) on more than 8 other devices, always without any problems.
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
user_name_duplicate said:
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
Click to expand...
Click to collapse
P20 lite is not so bad, maybe you are doing something wrong...
I've installed without problems Havoc, LOS 16.0, LOS 17.1unofficial, AOSP 10, losq-v224-201017 etc. etc...
P.S.: If you "hate" Google and Google's bloatware (like me ) only, you can simply rebrand your phone to chinese Nova 3e.
Or, choose Custom ROM based on Stock with KangVip settings , stable enough to be used as your daily driver." ( e.g. https://forum.xda-developers.com/hu...m-emui-8-0-kangvip-p20-lite-catuva21-t3813564
https://forum.xda-developers.com/hu...-emui-8-0-0-huawei-p20-lite-dual-sim-t3813604) . Using KangVip settings you can disable completely GAPPs .
(My primary phone is at the moment Mate 10 lite rebranded to chinese Maimang 6 (to get away from GAPPS ) . Among other things, better battery life, lower data consumption (using FUT) etc.)
Hi -Alf-, thank you for replying.
-Alf- said:
P20 lite is not so bad, maybe you are doing something wrong...
Click to expand...
Click to collapse
You're right, it's not the phone, it's me. I guess I am doing something wrong, but I don't have the slightest clue what that is.
Any suggestions?
I've already invested a lot of time and have more or less resignated, but thanks to covid lockdown I'm basically trapped inside the house and might aswell give it another try.
Rebranding is an option, you're right. I already have downloaded a nova 3e Firmware, if nothing else works, I might try that.
Also, I'll have a look at the KangVip Roms, haven't heard of them before.
But to be honest, I think I wouldn't be satisfied with those options, at least not for a long time.
Getting lineage running on that phone is a task, the problem solver inside me is really commited to accomplish, because that was the intention I bought the phone with. Also, not being able to accomplish something that hundreds of other people already have done and that is proven to work is driving me nuts. I wouldn't have bothered trying to get it working for 10 days otherwise.
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Try Havoc 2.9 (requires EMUI 8)
Havoc 2.9
Hi -Alf-,
-Alf- said:
Try Havoc 2.9 (requires EMUI 8)
Click to expand...
Click to collapse
Tried that now, after downgrading to EMUI 8 via HiSuite, I did exactly what you wrote in that thread. The outcome is the same as with every other ROM I've tried: I see the "your device has been unlocked and can't be trusted" screen, then after a while it tells me that "my device is booting now" and just does nothing except rebooting every 10 or so minutes.
Luckily those devices seem to be fairly indestructible, as long as the Bootloader is open and FRP is disabled, so I'll give it some more tries.
-Alf- said:
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Click to expand...
Click to collapse
I bought the phone because I thought it was officially supported:
LineageOS Downloads
download.lineageos.org
Was that assumption wrong, is there some hint or exception, that I'm not seeing?
The phone was delivered some weeks late because the seller was out of stock. I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
user_name_duplicate said:
I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
Click to expand...
Click to collapse
It may be a fake, try to verify the authenticity on linked website
imei24
user_name_duplicate said:
I guess it came directly from china
Click to expand...
Click to collapse
Exactly, I saw for example Huawei P20 Pro with MediaTek proc.
Btw., I have installed this Havoc 2.9 three times without problem, so it's really very strange...
In fastboot mode run commands :
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem get-product-model
fastboot getvar rescue_version
and post the results please.
Some might fail, so don't worry about it.
You can also download "Device Info HW" apk and check your SoC (Kirin 659) Vendor (HiSilicon), ABI (arm64-v8a) etc.
On imei24, the device is listed as "Huawei P20 Lite" for both imeis, blacklist status is "clean". Recognized Serial is the same for both Imei numbers.
Only thing that's not clear to me is the warranty status:
Warranty start: 2018/7/23
Warranty end: 2018/8/6
So it can't be that new, at least not factory new, right?
I bought it on real.de, so I have no further information where it comes from. China was just my assumption because they where out of stock and delivered 2 or 3 weeks late. I can't really imagine that real is selling fake phones (on purpose). That really wouldn't help their image if people found out.
I ran the commands you provided:
fastboot oem oeminforead-CUSTOM_VERSION: FAILED
fastboot oem oeminforead-SYSTEM_VERSION : ANE-LX1 8.0.0.180(C432)
fastboot oem get-build-number : ANE-LX1 8.0.0.180(C432)
fastboot getvar vendorcountry: hw/eu
fastboot oem get-product-model: ANE-LX1
fastboot getvar rescue_version: rescue0.6
I will download the Device Info apk as soon as my device boots again (I will reflash the stock image once again).
Edit: Device Info HW is telling me I'm using a Kirin 659 SOC.
Okay, most of custom ROMs require lower build number, that's why I wrote that I tested Havoc 2.9 on .126. If you are running latest build number, it may cause your problems.
IMO it is time to clean your phone, extract from Oreo firmware (it doesn't matter which build number) ramdisk.img , kernel.img, recovery_ramdisk.img and erecovery_ramdisk.img and transfer to the SD card.
Download .126 Service ROM
8.0.126
unpack it and transfer dload file to the SD Card (without unpacking it)
Install
TWRP
over eRecovery, boot into TWRP, select Flash image and flash 4 files. Go back to main TWRP's panel > Reboot > Power Off.
Use three button combo to flash the ROM. This process will erase all your data and lock the bootloader again!!!
Unlock BL and try Havoc 2.9 . It must work!
Good luck.
Edit: I found on my MEGA :
https://mega.nz/#!o8FUVR6T!-1fl6TviRtgGbssuG9LgyssCJg4dwxa84luJmrnvSCg
https://mega.nz/#!gkdgnLBa!O8LVZF4J0NiEB78c9z4_FxASN0vWx3rOAIQdmhApAOQ
https://mega.nz/#!xpViTTSC!Q_5ieeEL0gpKROj35cvjc_TRddmkFTMsIxvOT6lS23Y
https://mega.nz/#!EhM2lZqK!yphxvKNUQueIryop44DmPflp7Iwi9c8ExeaCRqA-iY4
Hello Alf, thanks for your last reply!
Downgrading worked, that was the last thing I've tried before christmas.
I wanted to continue today, but found this thread you've posted in.
I thought I'd give it a try and now I'm running on lineage (which is what I initially wanted), sadly only the 15.1 version, but I don't need the newest version.
WiFi is working and, until now, it's running stable. I've installed 8.1. nano gapps (might try pico in the future) and magisk v21.
Maybe I'm lucky and in the next few weeks or months I'll find a working build of an android pie lineage.
I think with installed TWRP it should now be possible, to do a complete backup, mess around with the system (i.e. upgrade Android/Flash ROMs) and then restore it to my now working state, is that correct?
If that's the case, I'll try some other ROMs, including the havok ROM I've already downloaded.
Which partitions must be included in my backup to perform such operations?
For anyone else encountering my problem, here is what finally did the trick:
Code:
- downgrade to .126, following alfs procedure
- Flash TWRP by pretoriano80 (on recovery_ramdisk partition)
- do a wipe (format data to get rid of encryption, then via advanced wipe format cache partitions and system)
- install lineage 15 (link), last build is from 2020-10-27, so it's not an abandoned build
- install GAPPS 8.1
- install magisk v21
- wipe cache/Dalvik
- boot to system
Booting for the first time took a few minutes, but since then, it's running smooth and without any problems.
The only thing that's still an enigma to me is, why the LOS builds I initially tried (with EMUI 9.0.0.200) didn't work, even though other people don't seem to have a problem with ANE-LX1 and LOS16. If anyone is reading this and has an answer to that question, please post!
For now, I'm happy with LOS 15. Thank you many many times, Alf! Greetings to Melmac!
user_name_duplicate said:
Thank you many many times, Alf!
Click to expand...
Click to collapse
No problem...
user_name_duplicate said:
Greetings to Melmac!
Click to expand...
Click to collapse
I'm currently struggling with the same issue. Tried every combination of TWRP with lineage 16 and gapps. Some roms I can get to boot but then not enough space for h gapps. I have tried to wipe system, data and cache to resize system partition which ends up in phone booting directly to TWRP. Other times I get to warning screen and end up with boot - loop. So I'm well a are off your frustration. However I have decided that I'm not gonna settle for version 15. I'm trying for 17 but much have to settle with lineage is 16..