DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
TWRP 3.1.1-0 for Huawei Nova
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes
1) It has been confirmed that's working on EMUI 4.1. However, it haven't been tested on EMUI 5 and i don't know if encryption is working. If it is working, you won't have to format /data. So, i would be glad if someone could test it.
2) I've chose the red color because it looks kinda cool and it's also easy to know which recovery you're using. In future, i may change it back to blue or i may change it to other color (like teal). I may also do it like @Meticulus did for his TWRP's (red color when you're on EMUI and blue when you're on LineageOS etc.) or maybe a new color every time you go to recovery lol.
3) There are still some things with blue color. I'll look into it more as I'd like to change the whole blue color. I wanna do it in the source code.
Click to expand...
Click to collapse
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
Requirements
Huawei Nova
Unlocked bootloader ( here's a guide about how to unlock it)
Click to expand...
Click to collapse
Installation
If you already have a TWRP installed:
1) Boot in TWRP.
2) Select "Install", then "install image".
3) Select the recovery.img where you've placed it and then choose recovery from the partition list.
5) Reboot recovery if you wanna boot in TWRP or reboot system.
Click to expand...
Click to collapse
If you don't have any TWRP installed:
1) Unlock your bootloader. Here's a guide about how to do it.
2) Run the following command in terminal (linux) or command prompt (windows, e.g. minimal ADB and fastboot):
Code:
[COLOR="red"]/* If you are doing this on Linux,
then run fastboot with [B]sudo[/B]: sudo fastboot blabla */[/COLOR]
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Download
AndroidFileHost | Mediafire
Sources
TWRP: https://github.com/omnirom/android_bootable_recovery/tree/android-7.1
Device tree: https://github.com/skinzor/android_device_huawei_hwcan/tree/android-7.1
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/cm-14.1
Click to expand...
Click to collapse
Credits
@abhishek987
@Meticulus
@ TWRP team
@ OmniROM
@ Huawei
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP 3.1.1-0, Tool/Utility for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/omnirom/android_bootable_recovery/tree/android-7.1
Version Information
Status: Stable
Stable Release Date: 2018-01-20
Created 2018-01-20
Last Updated 2018-01-20
Reserved
Reserved
Nice job on red TWRP...flashed and working great
not working on EMUI 5
we have to password to encrypt Data .... (lol no one know pw )
So we have to format Data like you said ....
Thanks for updates.
And waiting your kenel.
Do not know whether he supports Chinese? The red UI is cool and I want to try ?
To Young said:
Do not know whether he supports Chinese? The red UI is cool and I want to try ?
Click to expand...
Click to collapse
just trying ... no problem ... u can reflash old version
To Young said:
Do not know whether he supports Chinese? The red UI is cool and I want to try ?
Click to expand...
Click to collapse
If you meant chinese language, then it doesn't have it as far as i can see. If you meant the chinese model of Nova, well it should work on all models.
Just like @babysocola1x said, you can try.
babysocola1x said:
just trying ... no problem ... u can reflash old version
Click to expand...
Click to collapse
Thank you ?
---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------
#Henkate said:
If you meant chinese language, then it doesn't have it as far as i can see. If you meant the chinese model of Nova, well it should work on all models.
Just like @babysocola1x said, you can try.
Click to expand...
Click to collapse
I mean Chinese, I will try it
Nice, but how to make a nandroid backup ?
it dosnt mount any storage, i've even tried otg using a usb flash drive.
what gives?
Axims said:
Nice, but how to make a nandroid backup ?
it dosnt mount any storage, i've even tried otg using a usb flash drive.
what gives?
Click to expand...
Click to collapse
I don't have any problem with backups. I've made backups and restored them without any problem. As for OTG, I don't have the possibility to test that.
Please share the recovery log.
#Henkate said:
I don't have any problem with backups. I've made backups and restored them without any problem. As for OTG, I don't have the possibility to test that.
Please share the recovery log.
Click to expand...
Click to collapse
Well, seems the sd card was buggy, replaced it with a new samsung evo and
everything went smooth from there. (seems ext sd is the only selectable storage).
Now, have you noticed the warning about "project" part during backup?
is it normal?
Axims said:
Now, have you noticed the warning about "project" part during backup?
is it normal?
Click to expand...
Click to collapse
I'm not sure what you mean and I don't remember seeing this, but it's also possible that I've just missed it.
Could you share a screenshot? You can take screenshots in recovery just like you do when your phone is booted. You can also share a recovery log.
Actually, It's Product no Project!
I PM'd you the recovery.log
nothing important I guess?
Axims said:
Actually, It's Product no Project!
I PM'd you the recovery.log
nothing important I guess?
Click to expand...
Click to collapse
I haven't received any PM. Maybe it's XDA's fault as it looks like it's fucked up. All my posts were delayed today and noticed the same thing at other users.
Well, I didn't have this problem, but /product has some files (like acdbata, needed for audio) which EMUI uses and LineageOS or other ROMs too (since it's using blobs from EMUI). So, this could be a problem for ROMs like Lineage, but I think you can just fastboot the product.img after you extract it from update.app (stock firmware).
You can also try to restore this TWRP backup of product partition and restore it.
#Henkate said:
I haven't received any PM. Maybe it's XDA's fault as it looks like it's fucked up. All my posts were delayed today and noticed the same thing at other users.
Well, I didn't have this problem, but /product has some files (like acdbata, needed for audio) which EMUI uses and LineageOS or other ROMs too (since it's using blobs from EMUI). So, this could be a problem for ROMs like Lineage, but I think you can just fastboot the product.img after you extract it from update.app (stock firmware).
You can also try to restore this TWRP backup of product partition and restore it.
Click to expand...
Click to collapse
Thanks, as you may read the log later, it gave 2 errors at beginning and the end that it could not read or open Product. something like that.
I'm still on B151 MM Rom , will this backup of product work with any version?
Ok , my fear came true, long story short: I installed latest rom via FF app and bootloop began.
tried many ways, didnt work. flashed twrp again and tried to restore that nandroid backup, turns out those 2 errors were serious: failed to mount cust, failed to mount product, system goes near end then another error and quits. only boot and data seems restored fine.
while i'm going to try that smoochi's backup (bless him) , can you please recheck to see if my case was some isolated issue or there is something to fix about this reccovery?
thanks
Hi...youve learned the lesson...never install from FF...ive been using twrp for quite a while on my nova plus and never had such problems except once cuz i tried to restore a backup that ive done format/data...then got into bootloop..
What are you planning to use...emui4 or 5 ?
virusdunil said:
Hi...youve learned the lesson...never install from FF...ive been using twrp for quite a while on my nova plus and never had such problems except once cuz i tried to restore a backup that ive done format/data...then got into bootloop..
What are you planning to use...emui4 or 5 ?
Click to expand...
Click to collapse
I was on emui 4 (B151) everything was fine until I got an itch to try android 7!
Ok, I restored with smoochi backup then updated to B341 , now cust is gone
(no update in setting either) so went to reflash this twrp , but it seems unlocking bootloader is not enough, now says FRP locked! wtf??
I already hate this android 7! I'll get back to 6 first chance i get !
I had same problem...theme manager not working...file and updade manager gone so...
Frp locked is OEM unlock in developement...it must be ON...
Im still on emui4 and will stay on it ?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My-RoM based on clear stock B609. System is slimmed down with unnecessary applications and add-ons and You can install it simply by custom recovery (CWM).
In my idea every custom ROM it should be a stable and smoother minimal base for other users to customize and experiment it by own.
My-RoM current version: v3.3 (B609)
AnTuTu result:
Features:
Full Rooted
Removed unwanted apps
Caller picture re-sized
AddAway
Xposed
xLed - Custom led notifications
Double tap to sleep
Clock color changer
CrappaLinks
Holo Light Reboot
Swiftkey Keyboard
Kitkat External Card fixed
Boot sound removed
Custom splash
Custom boot animation
Other changes...
Known bugs:
If You found report
Requirements:
Bootloader unlocked
EMUI 3.0 ROM installed.
If you currently on EMUI 2.3 than update it to B602 or B609 ROM.
Download:
My-RoMv3.3.zip
Installation: (All wanted files inside package !)
Backup your important data (use HW Backup application)
Unpack downloaded files to external SD card
Install Stock recovery B609 (by fastboot) and wipe data/factory reset (by stock recovery)
Install CWM recovery (by fastboot)
Install P7-My-RoM_v3.3.zip (by CWM recovery)
Install SuperSU-v2.40.zip (by CWM recovery)
Reboot
When CWM ask for fixing root - select YES
Configure system
Settings -> Screen saving -> On
Open XPosed app
Modules -> Select all (or wanted) preinstalled modules
Framework -> Installation mode -> Disabled resource hooks
Framework -> Install/update
Reboot
Open HW Backup
Restore data from backup
Gaps to optional installation by CWM
Swype keyboard
Sim Tool Kit
My-RoM_gapps.zip
Remains !
If somebody don't want my custom logo/splash or boot animation just install (by CWM recovery) original one from downloaded package (HW_oem_logo.zip or HW_oem_anim.zip).
Reverting to EMUI 2.3 ROMs
Just install your old ROM by local update (sc card/dload/update.apk)
Previous versions:
My-RoM v3.1 (B602)
My-RoM v3.2 (B609)
Notice !
Everything you are doing on your own RISK !
Donators:
Godworrior1 - 5 USD
Fuijj - 1 USD
Mik Komarov - 10 USD
Shifa - 5 USD
rubberduck84 - 10 EUR
Thanks very much for donators
http://forum.xda-developers.com/donatetome.php?u=6041257
Credits:
Google
Huawei
Razziell
Shaftamle
XDA users
Swiftkeys
Everyone who compiled at least one line of included aps !
----------------------------------------------------------------------------------------------------
XDA:DevDB Information
My-RoM, ROM for the Huawei Ascend P7
Contributors
Ziolek67
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: B602 or later
Version Information
Status: Stable
Current Beta Version: 3.3
Beta Release Date: 2015-01-18
Created 2014-12-18
Last Updated 2015-02-08
Welcome to the arena
Welcome back to the arena for developers and common users like me, who enjoy testing and installing technological stuff for fun or for work. I hope you can give the credits to the people who deserve it, and to design your own projects as well. You are famous, people from HTC mania have tested your roms too. Happy to see you again !!!!:good:
2 hours with the rom and.....
I tested almost all the rom 3.1 and you are doing an excellent job since s-view cover is fixed, now you can record phone calls. it has only essential apps for daily use. it is stable so far. Antutu Benchmark gave me 29000..
Humble Recommendation: you do not need to put "Myrom" in the first booting screen. All people who use your rom will know what rom it is about. How about eliminating "HICARE", who cares to know the phone numbers of Huawei or send messages to huawei staff. If you need them just google it or email it. Finally how about eliminating the browser or at least the shortcuts and place another custom browser in it like chrome, Maxthon,etc. I hate to see things in chinese like this:
It's possibile upgrade from MyRom 3.0 ?
How can I downgrade to b133 for reinstall all with clean installation??
It is very simple
teto78 said:
How can I downgrade to b133 for reinstall all with clean installation??
Click to expand...
Click to collapse
I have written this procedure several times in different posts. You must put B133 file called UPDATE.APP in a carpet called /dload/ in the sd card, you can create it. then install it via update---local update. That's it (Remember put the stock recovery 3.0 before performing actions for downgrading).
Godwarrior1 said:
I ...you do not need to put "Myrom" in the first booting screen. ...
Click to expand...
Click to collapse
Inside uploaded ROM package is HW_oem_logo.zip which include stock Huawei splash screen and script to install it.
If somebody don't like my splash screen can just install it by recovery after ROM installation. That is possible also to use this script to installing your own logo/splash accordingly to my tutorial.
Godwarrior1 said:
How about eliminating "HICARE", who cares to know the phone numbers of Huawei or send messages to huawei staff. If you need them just google it or email it. Finally how about eliminating the browser or at least the shortcuts and place another custom browser in it like chrome, Maxthon,etc. I hate to see things in chinese like this:
Click to expand...
Click to collapse
Hm... some people hate stock browser but some ask about it . ROM is fully rooted and it it's easy to deleting this apps by Root Explore. Next version (if will) I'll try to install as user applications. In that case it'll be easy to uninstalling it by user. But I remember from previously roms that stock browser can't work properly as user application. We'll see.
onurb said:
It's possibile upgrade from MyRom 3.0 ?
Click to expand...
Click to collapse
I think that is possible and it should work well. But I always recommend to make factory reset using stock recovery after every re installation from other versions.
Finally.
In my idea every custom ROM it should be a stable and smoother minimal base for other users to customize and experiment it by own. :fingers-crossed:
I made clean install..ROM works very well..clap clap !
Not working
Followed the procedure yet stuck on booting after flashing Rom and Kinguser. It stuck on booting and go into recovery instead. And now my phone is locked! When I connect my phone through fastboot, it is detected as the Lenovo Composite Device. What the heck is happening?
Free to choose
Finally.
In my idea every custom ROM it should be a stable and smoother minimal base for other users to customize and experiment it by own. :fingers-crossed:[/QUOTE]
Exactly,
so in my opinion you don't need to put any app that anyone can do it by himself.
Neither xposed or keyboard ,anything at all.
btw- good work
Cannot download the file
Is there any other link. I try to download the file and almost at the end I got a network error. Is there any other way to download the files. I really love your ROMS as they are super smooth. Please help.
I always recommend
amruhaidy said:
Followed the procedure yet stuck on booting after flashing Rom and Kinguser. It stuck on booting and go into recovery instead. And now my phone is locked! When I connect my phone through fastboot, it is detected as the Lenovo Composite Device. What the heck is happening?
Click to expand...
Click to collapse
I always recommend installing CWM Recovery before installing any custom Rom and do a full wipe of data and wipe dalvik cache to eliminate all traces from the old rom. Another thing I recommend to see if you come from 2.3 to 3.0 emui, you must install the right /dload/ Filein the sdcard, and to have factory recovery and the installation should be executed with the options update/local update.
[Solved] Force update B133SP01
Godwarrior1 said:
I always recommend installing CWM Recovery before installing any custom Rom and do a full wipe of data and wipe dalvik cache to eliminate all traces from the old rom. Another thing I recommend to see if you come from 2.3 to 3.0 emui, you must install the right /dload/ Filein the sdcard, and to have factory recovery and the installation should be executed with the options update/local update.
Click to expand...
Click to collapse
Thanks for your response but I've actually mentioned that I've had followed the instructions, none was left behind so obviously I've has flashed CWM Recovery first and did the rest. Anyhow, I have solved the problem myself. Here's the funny thing, my device was locked (seen from bootloader), I have EMUI3.0 on, I put B133SP01 update.app in the dload and force update. Somehow, I have my phone working again with B133SP01 installed and EMUI2.3 on board! Funny when it's not supposed to work out since downgrading from EMUI3.0 to 2.3 is a daunting task. But Thanks again for your response, I really appreciate it. Merry Christmas! :cheers:
The same to you
amruhaidy said:
Thanks for your response but I've actually mentioned that I've had followed the instructions, none was left behind so obviously I've has flashed CWM Recovery first and did the rest. Anyhow, I have solved the problem myself. Here's the funny thing, my device was locked (seen from bootloader), I have EMUI3.0 on, I put B133SP01 update.app in the dload and force update. Somehow, I have my phone working again with B133SP01 installed and EMUI2.3 on board! Funny when it's not supposed to work out since downgrading from EMUI3.0 to 2.3 is a daunting task. But Thanks again for your response, I really appreciate it. Merry Christmas! :cheers:
Click to expand...
Click to collapse
The same to you. Merry Christmas and Happy New Year !!!!
amruhaidy said:
... I've has flashed CWM Recovery first and did the rest. Anyhow, I have solved the problem myself. Here's the funny thing, my device was locked...
Click to expand...
Click to collapse
Hm... I am wondering what could happen with your device. First time I hear about situation that bootloader was locked during flashing room. Are you sure that you flash appropriate files (especially recovery or kernel) by fastboot? What was you previous system?
bolleyjara said:
Is there any other link. I try to download the file and almost at the end I got a network error. Is there any other way to download the files. I really love your ROMS as they are super smooth. Please help.
Click to expand...
Click to collapse
Mirror added to first post.
Ziolek67 said:
Hm... I am wondering what could happen with your device. First time I hear about situation that bootloader was locked during flashing room. Are you sure that you flash appropriate files (especially recovery or kernel) by fastboot? What was you previous system?
Wysłane z mojego HUAWEI P7-L10
Click to expand...
Click to collapse
Hahaha..it keeps me wondering even till now. I've been around a few roms and I know how to work things out so yeah I really followed the instructions. My previous rom was Se7en and if you are going to say wipe dalvik and full wipe, believe mw, I did it already..haha
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Wow… fast and no lags ?
The perfect rom ever.
But I use superuser pack from v3.0 its work like charm and its full rooted
:thumbup:
Thanx a lot
Sent from my HUAWEI P7-L10 using XDA Free mobile app
If somebody have any problems after installation it means that they didn't installation procedure exactly. Especially wiping data before installation by using the supplied stock recovery.
I suggest that if you previously used custom rom that reset factory data (by supplied B602 stock recovery ) also after installation My-RoM and reinstall it again (kinguser too) .
It is important to totally removing any remains of previous rom.
Notice! TWRP doesn't wiping all data correctly. Use stock recovery to do this exactly.
Sent from my HUAWEI P7-L10
Ziolek67 said:
If somebody have any problems after installation it means that they didn't installation procedure exactly. Especially wiping data before installation by using the supplied stock recovery.
I suggest that if you previously used custom rom that reset factory data (by supplied B602 stock recovery ) also after installation My-RoM and reinstall it again (kinguser too) .
It is important to totally removing any remains of previous rom.
Notice! TWRP doesn't wiping all data correctly. Use stock recovery to do this exactly.
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
can u add sound to your flashable stock boot animation zip please?
thnx
Hi folks
When I get back the device from Huawei services, I receive a boot.img without encryption that let me able to backup and restore the firmware hundred times without errors .
In this tutorial I'll show you how to do that without need to bring the phone to Huawei services to reset the software, starting from now can be done as well.
Requirements:
Unlocked bootloader, you know how to do that.
My own TWRP, that authorized Huawei store told should use my own TWRP to restore the phone, so get it from here by downloading the latest version.
Stock firmware, click here to download it, it's for single sim only.
Stock IMGS that needed for decrypt and to re-enable the encryption once firmware has been done with restoration, click here to download them.
7 zip to unpack the tar.gz.
Code:
[CENTER][COLOR="Red"][SIZE="4"][FONT="Comic Sans MS"]Please read the steps carefully because I'm not going to repeat them for each user, thanks[/FONT][/SIZE][/COLOR][/CENTER]
Reset Steps:
Download the C432B161.
Unpack the .tar.gz archive with 7 zip.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rename from C432B161 to TWRP.
Copy to the Internal Storage.
Reboot to TWRP Recovery by the following command.
in the IMGS archive you will find a bootimage called boot.img, rename it to boot.emmc.win and copy to TWRP->BACKUPS->57UDU17709001769->2017-10-18--12-03-00_NRD90M_test-keys -> replace it and then follow the video
Go to the TWRP.
Wipe everything except the external_sd (the path where you copy the backup)
Tab on Restore.
Choose the copied backup make sure to rename from C432B161 to TWRP to match.
Select all partitions.
Swipe the screen and wait until finish.
Reboot to bootloader once done.
In the IMGS.tar.gz there is a file caller boot.img flash via fastboot as boot and will get booted like charm
Warning:
You are not allowed to copy or steal the files of my guide without ask my permissions.
Because I take almost week to upload the firmware after many times of failing upload.
Mention this guide for who looking helps to restore this device.
If I saw any piece of my contents in other threads, I'll report as abuse and ask a moderator to close his thread because I already saw someone rename my recovery and put it inside his thread without asking permission. that's all.
This guide could be helpful for who want to debrand his device, so we need tester.
to enable dual sim: you must flash an oeminfo partition from dual sim firmware.
Happy restoring.
Can I change from dualsim to monosim with this guide?
Wire1122 said:
Can I change from dualsim to monosim with this guide?
Click to expand...
Click to collapse
to be honest, I can't confirm since is the full backup from my single device.
in case dual sim still appear even after restore, you have to flash the single sim oeminfo partition.
when I must flash oeminfo?
Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
post firmware restoring
Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
not works to me. Pralx1c432b182 such before restoring
Wire112233 said:
not works to me. Pralx1c432b182 such before restoring
Click to expand...
Click to collapse
whats not work restoring firmware or converting from dual to single?
haky 86 said:
whats not work restoring firmware or converting from dual to single?
Click to expand...
Click to collapse
converting from dual to single. But after restoring the fw remains b182, not 161
Wire112233 said:
converting from dual to single. But after restoring the fw remains b182, not 161
Click to expand...
Click to collapse
yup because some partitions is upgraded to b182 (dual sim), same thing happen to me b181 (single sim). for converting to single sim, I'll upload the oeminfo partition soon.
Note: this operation might will lock bootloader/frp automatically, so I recommend to check them via fastboot mod.
When oeminfo?
Sent from my HUAWEI PRA-LX1 using XDA Labs
Looks like the images gone bad, and now point:
Wipe the following partitions like in the screenshot.
Click to expand...
Click to collapse
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Sixter said:
Looks like the images gone bad, and now point:
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Click to expand...
Click to collapse
might the elite rom v6 cause that issue, try to restore it again perhaps it will gone..I didn't get that green and red screen
Hey, any have oeminfo for single sim fw? its impossible to find
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Wire1122 said:
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Click to expand...
Click to collapse
Thanks for the help! For what version is this oem? (b161?)
dannyzamora said:
Thanks for the help! For what version is this oem? (b161?)
Click to expand...
Click to collapse
I don't know Sorry It is monosim c432
Wire1122 said:
I don't know Sorry It is monosim c432
Click to expand...
Click to collapse
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
dannyzamora said:
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
Click to expand...
Click to collapse
even if downgraded will keep on b182 because some partitions will not downgraded since my twrp is designed to backup/restore only necessary partitions for fully worked firmware.
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
bagage said:
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
Click to expand...
Click to collapse
You might want to try the Recovery MITM approach but its a tad more complicated. https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/guide-local-recovery-server-t3714900
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sony AOSP project
Disclaimer
I'm not liable for anything YOU do to YOUR device, YOU are doing it and it's YOUR device.
What is it?
It's a project developed and maintained by Sony Xperia Developers team.
You can get more informations here: https://developer.sony.com/develop/open-devices/
Can I build it by myself?
Sure, just follow these instructions and have patience!
What works and what doesn't?
According to this official page, almost everything seems to be fine.
How can I flash it?
Follow these steps:
Unlock the bootloader (this will erase your data and will void warranty): https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Setup fastboot on your PC (there are many guides for this step)
Download and unpack the zip archive
Open a shell into the folder containing unpacked files
Run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (it’s not necessary to flash userdata every time)
Download and unpack the corresponding vendor image from here: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open a shell into the folder containing unpacked image
Run this command:
fastboot flash oem SW_binaries_for_Xperia_xxxxx.img (where "xxxxx" varies depending on the file)
(optional) In case you want to flash GApps, Magisk or other mods, you can use TWRP: https://forum.xda-developers.com/xa2-ultra/development/recovery-twrp-3-2-1-0-touch-recovery-t3774193
Reboot the device and enjoy!
Download link
You can get the builds from my AFH folder: https://androidfilehost.com/?w=files&flid=269497.
I haven't done any change to Sony's source code, these are vanilla builds.
Credits
All credits go to Sony and Google.
XDA:DevDB Information
Sony AOSP, ROM for the Sony XA2 Ultra
Contributors
axxx007xxxz
Source Code: https://github.com/sonyxperiadev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-08
Reserved
NOTE: I'm in no way associated with Sony, these are unofficial builds and are made for pesonal usage.
Also, these builds are untested so I can't assure they're going to work!
Reserved 2
Post reserved for future usage.
Reserved 3
Post reserved for future usage.
Reserved 4
Post reserved for future usage.
New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r20
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 81032020581dd636ab9d7f8414609bad07332288
Last commit of sonyxperiadev/kernel: 1df958f2943c6c5cae31018e42d2f42e8a55c4b3
Last commit of sonyxperiadev/device-sony-nile: c775da101d57377979cdcb79b1ba1b5bbd3739a4
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=818222786056029296.
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying. And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it.
Click to expand...
Click to collapse
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
roirraW "edor" ehT said:
I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Casserole said:
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Click to expand...
Click to collapse
You're welcome! I'm not suggesting that you flashing Magisk or anything is the cause of this on this ROM, it's just related to changes in Android 8.1 and that it doesn't really necessarily mean there's something wrong. I'm sure there are ways around it, but since I'm not a developer and I don't know what triggers it, I don't know.
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
tombassi said:
cool down dude !! XDA is not the correct please for these bad words. if you don't know what you are doing that is not the Developer fault and if you need no bugs stay with the stock ROM.
Click to expand...
Click to collapse
Thanks! With "almost everything seems to be fine", I meant that most of the main parts (should) work.
Camera is a known problem on Sony devices due to DRM keys getting erased on bootloader unlock.
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Click to expand...
Click to collapse
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
then reboot the phone and test.
These come directly from H4113 makefile, I can't assure you everything will be fine after this, but you can give it a try.
As per the fingerprint, it's currently broken on all variants, I'm sorry.
mirco_pa said:
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
Click to expand...
Click to collapse
Sony website reports it as currently not working on AOSP, I'm sorry.
axxx007xxxz said:
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Click to expand...
Click to collapse
I think SD card problem was related to something else, because it started working after reformatting.
But there were also problems with SIM card, it worked on first boot, but after removing and inserting it again device shown that there were no signal, so your solution may be helpful in this situation. I can't test it due to limited amount of time, though.
New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r26
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 1c992d7f3f2ef8d0b53397e23227e10489e40bec
Last commit of sonyxperiadev/kernel: ab6fd5b1a4126cfdd4391eefe8eba17eb6626781
Last commit of sonyxperiadev/device-sony-nile: 7d57c76da9ce47849429347e77e013781e63db2f
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=890278863836285554.
Can you build one for H4113? You shood have files for it too
Thanks axxx007xxxz for sharing these builds! They helped me recover Android on my completely wiped h3113 pioneer. Both the 8.0 and 8.1 build work for me. Downloading them to my PC was the hardest part, for some reason the download often fails.
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Thank you!
roirraW "edor" ehT said:
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I get the same error message right after booting, also without root. It's annoying, but I guess I can live with it.
P.S. As I'm a new user, I cannot use links yet. Please use these footnotes instead:
*: https[colon]//developer[dot]sony[dot]com/develop/open-devices/downloads/software-binaries
**: https[colon]//developer[dot]sony[dot]com/develop/open-devices/guides/aosp-build-instructions/build-aosp-nougat-8-1-oreo-4-4/#tutorial-step-6
1. parts of android which are closed source, graphics driver for example. you won't see them.
2. eng should give you more debugging options, like working adb logcat without enabling developer options which is sometimes needed while you're porting android to new device and there's just black screen on the phone for example. correct me if i'm wrong.
3. flashing worked through twrp for me but i had to build unsingned zip.
regarding the internal problem message, just ignore it.
davidhozic said:
Can you build one for H4113? You shood have files for it too
Click to expand...
Click to collapse
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Nonstop decay said:
Downloading them to my PC was the hardest part, for some reason the download often fails.
Click to expand...
Click to collapse
Unfortunately, Android File Host is problematic sometime.
Nonstop decay said:
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Click to expand...
Click to collapse
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
axxx007xxxz said:
I can make a H4113 build if you want to test it though.
Click to expand...
Click to collapse
Just wondering aside from not being supported in Sony's open device program what exactly is needed to get the H3223 from getting AOSP 8.1 built for it? I can't imagine the kernel being much different on the H3223 from any of the other XA2 Ultra single sim models, right?
axxx007xxxz said:
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Unfortunately, Android File Host is problematic sometime.
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
Click to expand...
Click to collapse
Yes plese make a build for H4413, i get so many random errors and every time i fix an error there appears another. And is the build for this model supposed to work with h4113? Aren't the boot images incompatible?
Hey,
I am in trouble with the K20 Pro (raphael). The first day I bought the device, I installed EU ROM v10.3.17.0 and used for a while. There was no problem. After that, I installed Magisk-v19.3.zip from TWRP and MagiskManager-v7.3.2.apk when Android booted. I just checked to see root privileges. I saw the ROOTED from the a root checker program. Afterwards, I had to transfer the IMEI number of my old phone to the new phone. Therefore, i updated the both IMEI numbers via COM port using WriteDualIMEI program. (adb shell -> su setprop sys.usb.config diag) Finally, I have a bootloop problem on my phone for 2 days. Android is not booting in any way.
What I have tried until now:
1. Installed xiaomi.eu_multi_HMK20ProMI9TPro_9.8.22_v10-10 on PitchBlack-raphael-2.9.0-20190708-0004 (Endless android booting stuck)
2. Format Data -> "yes" and Wipe Cache & Dalvik & System & Data & Vendor & Internal Storage and then installed xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9 (bootloop stuck)
3. I don't know in which situations but sometimes I get "No OS Installed! Are you sure you wish to reboot?" error after installing ROM.
4. Only happened once: Android booted and white spinning progress circle appeared at center on screen. After spinning for 60 seconds, it redirected to the TWRP menu.
Current status: I flashed Fastboot ROM (raphaelin_in_global_images_V10.3.5.0.PFKINXM_20190816.0000.00_9.0_in_5d0a303019) on Fastboot via MiFlash 2018..11.15.0. But i got "not catch checkpoint" error when the process is finished. It Redirected to Redmi-Recovery 3.0 screen. At the bottom of the screen, there was a error: NV data is corrupted
Is my device bricked? How can i fix that?
Thanks
Device: K20 Pro (raphael)
TWRP: 3.3.1-2
Fastboot
Unlocked
P.S: I apologize if there are grammatical errors.
Dentrax said:
Hey,
I am in trouble with the K20 Pro (raphael). The first day I bought the device, I installed EU ROM v10.3.17.0 and used for a while. There was no problem. After that, I installed Magisk-v19.3.zip from TWRP and MagiskManager-v7.3.2.apk when Android booted. I just checked to see root privileges. I saw the ROOTED from the a root checker program. Afterwards, I had to transfer the IMEI number of my old phone to the new phone. Therefore, i updated the both IMEI numbers via COM port using WriteDualIMEI program. (adb shell -> su setprop sys.usb.config diag) Finally, I have a bootloop problem on my phone for 2 days. Android is not booting in any way.
What I have tried until now:
1. Installed xiaomi.eu_multi_HMK20ProMI9TPro_9.8.22_v10-10 on PitchBlack-raphael-2.9.0-20190708-0004 (Endless android booting stuck)
2. Format Data -> "yes" and Wipe Cache & Dalvik & System & Data & Vendor & Internal Storage and then installed xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9 (bootloop stuck)
3. I don't know in which situations but sometimes I get "No OS Installed! Are you sure you wish to reboot?" error after installing ROM.
4. Only happened once: Android booted and white spinning progress circle appeared at center on screen. After spinning for 60 seconds, it redirected to the TWRP menu.
Current status: I flashed Fastboot ROM (raphaelin_in_global_images_V10.3.5.0.PFKINXM_20190816.0000.00_9.0_in_5d0a303019) on Fastboot via MiFlash 2018..11.15.0. But i got "not catch checkpoint" error when the process is finished. It Redirected to Redmi-Recovery 3.0 screen. At the bottom of the screen, there was a error: NV data is corrupted
Is my device bricked? How can i fix that?
Thanks
Device: K20 Pro (raphael)
TWRP: 3.3.1-2
Fastboot
Unlocked
P.S: I apologize if there are grammatical errors.
Click to expand...
Click to collapse
Try to fastboot flash MIUI 10.3.16.0 without locking bootloader.
I have no catch checkpoint error too but It automatically boots into MIUI.
overcustom said:
Try to fastboot flash MIUI 10.3.16.0 without locking bootloader.
I have no catch checkpoint error too but It automatically boots into MIUI.
Click to expand...
Click to collapse
How can i get MIUI Fastboot 10.3.16.0 ROM? I couldn't find here. I found the V10.3.8.0PFKCNXM Fastboot
Why do you play with IMEI numbers?
Dentrax said:
How can i get MIUI Fastboot 10.3.16.0 ROM? I couldn't find here. I found the V10.3.8.0PFKCNXM Fastboot
Click to expand...
Click to collapse
https://www.miui.com/shuaji-393.html
Scroll down and you will see k20 pro link. Just download it. Its from the official MIUI chinese site. You will only get the latest fastboot rom available. Right now its 10.3.16.0
Kollachi said:
Why do you play with IMEI numbers?
Click to expand...
Click to collapse
I just wanted to transfer my old phone's IMEI number.
Dentrax said:
I just wanted to transfer my old phone's IMEI number.
Click to expand...
Click to collapse
Hmm but why? I don't see any sense there.
Kollachi said:
Hmm but why? I don't see any sense there.
Click to expand...
Click to collapse
If the IMEI tax is expensive in your country, it makes sense.
theincognito said:
https://www.miui.com/shuaji-393.html
Scroll down and you will see k20 pro link. Just download it. Its from the official MIUI chinese site. You will only get the latest fastboot rom available. Right now its 10.3.16.0
Click to expand...
Click to collapse
Thank you, but;
Still same Nv data corrupted error. I think, i need to fix my IMEI and EFS partition first. :crying: I've been trying for two days.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, I fixed that problem. I copied the EFS to TWRP/BACKUPS/your_serial_number/. i had previously backed up. I used the LR team's TWRP, see here. Thank you @theincognito
I installed this ROM via Fastboot, i don't like it. There are so many dipsh*t CN apps and fonts are weird. It's like I'm using the phone in two languages. I am thinking about to install 10.3.17 EU ROM, is that worthy? Or should i install 9.8.29 Q ? I just want everything to be stable, new and up-to-date. Thanks...
Dentrax said:
Okey, Finally, I fixed that problem. I copied the EFS to TWRP/BACKUPS/your_serial_number/. i had previously backed up. I used the LR team's TWRP, see here. Thank you @theincognito
I installed this ROM via Fastboot, i don't like it. There are so many dipsh*t CN apps and fonts are weird. It's like I'm using the phone in two languages. I am thinking about to install 10.3.17 EU ROM, is that worthy? Or should i install 9.8.29 Q ? I just want everything to be stable, new and up-to-date. Thanks...
Click to expand...
Click to collapse
Install EU. P or Q, its upto you. In my opinion, Q EU is stable enough.
theincognito said:
Install EU. P or Q, its upto you. In my opinion, Q EU is stable enough.
Click to expand...
Click to collapse
Do you mean EU Android Q 9.8.8 ? What is the difference between 10.3.17 and 9.8.8? Version went backwards but the Android is Q. Are the MIUI versions same?
Dentrax said:
Do you mean EU Android Q 9.8.8 ? What is the difference between 10.3.17 and 9.8.8? Version went backwards but the Android is Q. Are the MIUI versions same?
Click to expand...
Click to collapse
I mean, EU 9.8.22 Android Q. 10.3.17 and 9.8.22 are different.
Dentrax said:
Do you mean EU Android Q 9.8.8 ? What is the difference between 10.3.17 and 9.8.8? Version went backwards but the Android is Q. Are the MIUI versions same?
Click to expand...
Click to collapse
9.8.8 is beta rom, released on 201'9'-0'8'-0'8'
10.3.17.0 is stable miui 10 rom.
The reason latest beta rom seems backdated than stable rom because of the naming scheme. Beta roms actually has most recent elements than stable roms.
Dentrax said:
Finally, I fixed that problem. I copied the EFS to TWRP/BACKUPS/your_serial_number/. i had previously backed up. I used the LR team's TWRP, see here. Thank you @theincognito
I installed this ROM via Fastboot, i don't like it. There are so many dipsh*t CN apps and fonts are weird. It's like I'm using the phone in two languages. I am thinking about to install 10.3.17 EU ROM, is that worthy? Or should i install 9.8.29 Q ? I just want everything to be stable, new and up-to-date. Thanks...
Click to expand...
Click to collapse
How do you install the LR teams twrp? stuck in a similar situation with no OS, recovery, and stuck in a fastboot loop. miflash gives checkpoint error
Dentrax said:
If the IMEI tax is expensive in your country, it makes sense.
Click to expand...
Click to collapse
Holy cow excrement?! WTF? Why do they tax that thing when it's basically free for everybody else in the world?
plskillme said:
Holy cow excrement?! WTF? Why do they tax that thing when it's basically free for everybody else in the world?
Click to expand...
Click to collapse
Because, IMEI legal registration fee must be made for each phone that brought from abroad. It's about ~$266. And K20 Pro ~$345, Also %18 VAT, Also %25 Special Consumption Tax, Also %6 TRT Bandrol, And finally the base price $345, which is 1978₺ Turkish Liras, comes to an average of ~4500₺ Liras which is ~$785. I'm buying one for myself, and one for the government. If you take a phone from abroad and try to bring it into the own country, you have to pay ~618₺ Liras free to legal registration which is ~$110. Shortly, iPhone 11 Pro Max 512G ($1499) comes to $2614. Pêrfecto!
No IMEI, MAC, damaged sensors
I have the following problem:
I made a Nandroid backup with TWRP without knowing that I was not able to RESTORE, playing a bit for the system fell into Hard brickeo ... revived from there I only remain without working IMEI, Wifi and sensors. I cannot restore my backup since my TWRP could not, what I already did:
+ Flash Rom stock with MiFlash
+ Flash Persist.img with TWRP
My question is if I can restore that backup with a different TWRP and how can I do without dying since I tried and stayed dead once.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Another weebified custom ROM aiming to be a home for weebs - Based on Project Materium, an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Click to expand...
Click to collapse
We offer vanilla, GApps and AuroraOSS variants. If you install a vanilla variant, the only supported GApps package is MindTheGapps (GApps/AuroraOSS builds are not available for a few devices due to space issues).
Download & instructions:
Install MIUI 12.5 if you have updated to anything Android 12.
Fully install custom recovery of your choice.
Flash the ROM. You can also sideload it with ADB if you want to.
!!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
After flashing, reboot to recovery.
Format data.
Flash Magisk if you want to.
Reboot to system and enjoy!
Download (Taken down due to discontinuation)
IMPORTANT: If you are coming from another ROM, you need to format data (TWRP > Wipe > Format Data > *type "yes"*).
IMPORTANT: If you want to keep Magisk after each OTA, you need to make it flash to inactive slot **right before rebooting** (Magisk > Install (In "Magisk" card) > Install to inactive slot)
About:
Features:
Latest security patches merged from LineageOS
SafetyNet passing unconditionally without Magisk/with kdrag0n's SafetyNet fix
Many optimizations coming from Stellar OS/Project Materium/droid-ng
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more! (We accept suggestions!)
What's working:
Almost everything
Bugs:
Microphone doesn't work when speaker is enabled during calls.
You tell me.
Sources are available at https://github.com/ProjectKasumi and https://github.com/Kasumi-Devices
Full list of device sources used;
Device tree
Linux kernel tree used
Vendor tree for proprietary blobs
ROM Founded By: Yuki (AITEx64)
ROM Developed By: Beru Hinode
ROM Designed By: Ayuko, Qirkl and UsiF.
ROM OS Version: 1.3 "PoPiPa" R2
ROM Kernel: Customized Linux 4.14.186 from MiCode
ROM Firmware Required: MIUI 12.5.16.0.RKLMIXM (Global)
Based On: Project Materium 1.0 (LineageOS 18.1)
Version Information
Status: Discontinued
Last Stable Version: 1.4 "PoPiPa"
SELinux Status: Permissive
Initial Release Date: July 20, 2022
poggers! atleast some buildbot didn't post it this time
J6idot said:
poggers! atleast some buildbot didn't post it this time
Click to expand...
Click to collapse
It wasn't even their build, they just took my build and posted it away! XD
Let's goo. Very awesome work here
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
solidamage said:
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
Click to expand...
Click to collapse
I could never get used to MIUI myself so I feel you. For custom ROMs, there are quite a lot built (buildbotted) with practically the same bugs as well; you can check them out in respective Telegram groups/channels!
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
It happens to me too ... Any advice?
Is this available on Android 12?
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Oxydeme said:
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Click to expand...
Click to collapse
yup did all the steps in the thread
nintendobuster420 said:
yup did all the steps in the thread
Click to expand...
Click to collapse
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
nintendobuster420 said:
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
Click to expand...
Click to collapse
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
still no fast charge, will keep it tough
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
@HistoriaXV @nintendobuster420 hope you could success flash in the next days
Oxydeme said:
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
Click to expand...
Click to collapse
System reports "Charging slowly" but my battery fully charges from ~10% in just 1.5~2 hours.
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
I have recently pushed a boot fix about this, you can flash it and format data to get it fixed.
Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
I use the OFOX from Woomy and it works with it too, so it's not recovery fault.
You mentioned firmware requirement there, good shot! Glad to see someone that's not from the development team finally noticing it!
Oxydeme said:
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
Click to expand...
Click to collapse
The vbmeta required is shipped along with the ZIP itself, so whether if you disable it or not, you can always keep verity enabled AS LONG AS YOU DON'T MODIFY ANYTHING INCLUDING INSTALLATION OF TWRP. The boot problem was due to some missing permissions required with Lawnchair 12.0, which was platform-specific issue. I have mitigated it as the lead developer of Kasumi and now just waiting for LineageOS to merge August '22 ASB on their Lineage 18.1 branches to ship newer builds. Until then, I have placed a little flashable that you can slap in on the recovery. It's global (means will work on all devices with latest Kasumi build installed). In fact, all it does is just putting the new permission XML file.
Oxydeme said:
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Click to expand...
Click to collapse
Not at all. Even though I have Secret, everything should be around the same across all variants, given that Woomy also tested it only for NFC during initial bringup before.
Oxydeme said:
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
Click to expand...
Click to collapse
The dedication and the hassle... My God, it's just pure inspiration to me. XD
Oxydeme said:
still no fast charge, will keep it tough
Click to expand...
Click to collapse
As I said previously, it's what system reports presumably due to some SEL denials. I tried to get as many as possible sorted out, still no luck. But just as a fact, it actually is fast charging.
Oxydeme said:
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
Click to expand...
Click to collapse
Well, thank you I guess. ^^;
Before I begin with replies to these, just referring to "dude", I'm a girl so I would prefer you calling me with "dudess" or "dudette" instead. Again, all up to you. No forces here.
The debloat is rather Lineage talent, I really just based on Materium and added things on top.
That 13 GB system partition is something that's coming from partition values from source, so whatever you do unless you flash GSI, it will always be 13 GB. See GitHub:Kasumi-Devices/[email protected]/BoardConfig.mk (Partitions section, BOARD_SYSTEMIMAGE_PARTITION_SIZE flag) for more info.
Eh, I still can't find a way to get CPU info properly, I guess it's related to kernel? Unsure though.
And some more tweaks will come as well, just stay tight! I'm working hard on another update! ;3
Sambit0789 said:
Is this available on Android 12?
Click to expand...
Click to collapse
Unfortunately no. Kasumi 1.x.x are all Android 11. Android 12 Kasumi will be possible only once our internal tests will be done and I finally finish working on Kasumi v2. Hundreds hyped, gradually widening audience, looking into the release of it. xD