https://sourceforge.net/projects/havoc-os/files/grus/
works perfectly, but the camera app it's ugly and obsolete, no battery drain with you change the network type to gsm/wcdma/lte, no bugs so far
Would love to see a real thread under Roms, Recoverys... with some more details and install instructions. Can't find so many details on sourceforge and from my personal feeling it would be nice to have an offical support thread here on XDA and not having to join telegram groups for every single Rom. Especially If it is called an offical one..
It installs, but then it stucks on the logo forever. Any idea how to flash?
secosan said:
It installs, but then it stucks on the logo forever. Any idea how to flash?
Click to expand...
Click to collapse
format data, you need baseband 11.0.1.0
gabi4175 said:
format data, you need baseband 11.0.1.0
Click to expand...
Click to collapse
How do I do that? There is no complete thread for this phone, hate it.
secosan said:
How do I do that? There is no complete thread for this phone, hate it.
Click to expand...
Click to collapse
in twrp flash this https://sourceforge.net/projects/mi9se/files/crDroid/Q/FW_Q_MIUI11.0.1.0.zip/download then go to wipe format data, type yes and that's all
The same core (Kowalski) as the crDroid and the same problems.
Bid battery drain in airplane mode, freezing after unlocking with fingerprint, etc.
So many bugs on the official build.......
dont know what i am doing wrong. Everytime i flash the Havoc 3.1.zip i get only Fastboot Mode. Flashing TWRP is not working anymore. I must flash via MIFlash to get TWRP back again.
1. flashed Global 11.0.6.0 with MiFlash.
2. flashed TWRP
3. flashed FW_Q_MIUI11.0.1.0
4. flashes Havoc 3.1
result is stuck in Fastboot and must flash again with MiFlash to get phone working again.
eagle*23* said:
dont now what i am doing wrong. Everytime i flash the Havoc 3.1.zip i get only Fastboot Mode. Flashing TWRP is not working anymore. I must flash via MIFlash to get TWRP back again.
1. flashed Global 11.0.6.0 with MiFlash.
2. flashed TWRP
3. flashed FW_Q_MIUI11.0.1.0
4. flashes Havoc 3.1
result is stuck in Fastboot and must flash again with MiFlash to get phone working again.
Click to expand...
Click to collapse
flash vbmeta
---------- Post added at 09:11 PM ---------- Previous post was at 09:11 PM ----------
eagle*23* said:
dont now what i am doing wrong. Everytime i flash the Havoc 3.1.zip i get only Fastboot Mode. Flashing TWRP is not working anymore. I must flash via MIFlash to get TWRP back again.
1. flashed Global 11.0.6.0 with MiFlash.
2. flashed TWRP
3. flashed FW_Q_MIUI11.0.1.0
4. flashes Havoc 3.1
result is stuck in Fastboot and must flash again with MiFlash to get phone working again.
Click to expand...
Click to collapse
flash vbmeta in fastboot
gabi4175 said:
flash vbmeta
---------- Post added at 09:11 PM ---------- Previous post was at 09:11 PM ----------
flash vbmeta in fastboot
Click to expand...
Click to collapse
flashing vbmeta after flashing havoc and when i stuck in fastboot mode ?
---------- Post added at 08:22 PM ---------- Previous post was at 08:12 PM ----------
when i try to flash "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" i get error " fastboot: unknown option -- disable-verity"
EDIT:
worked old ADB Version was the failure
Can somebody check SELinux status? Is it enforcing or permissive?
Hackis1 said:
Can somebody check SELinux status? Is it enforcing or permissive?
Click to expand...
Click to collapse
Pesissive, just checked.
secosan said:
Pesissive, just checked.
Click to expand...
Click to collapse
Has Havoc auto call recording?
dzidexx said:
Has Havoc auto call recording?
Click to expand...
Click to collapse
No it doesn't, from what I see.
3.2 was just released.
secosan said:
3.2 was just released.
Click to expand...
Click to collapse
OK. I'm very happy that Havoc OS is back for MI 9 SE. But there are some things that should be cleared. Will there be a thread in ROMs section at XDA. I have no telegram and therefore no info about development status. It would be nice if some peopele who have more informations post them here or better the developer of the ROM opens a thread for dicussions here at XDA.
Is there a changelog for Version 3.2. How is it about wifi calling like in CRDroid. Is it planned?
Thanks for replying.
Gesendet von meinem MI 9 SE mit Tapatalk
Not a stable rom, not for everyday use. I'm moving away.
calls not working
eagle*23* said:
flashing vbmeta after flashing havoc and when i stuck in fastboot mode ?
---------- Post added at 08:22 PM ---------- Previous post was at 08:12 PM ----------
when i try to flash "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" i get error " fastboot: unknown option -- disable-verity"
EDIT:
worked old ADB Version was the failure
Click to expand...
Click to collapse
what version adb working for you, sorry my bad english
Related
Fastboot rom install with -miflashtool
Xiaomi MI4 MIUI 8 Global ROM Alpha Test V 6.6.28 to V 6.7.5
http://bigota.d.miui.com/6.7.5/miui-ota-cancro_alpha_global-6.6.28-6.7.5-8f2c7836db-6.0.zip
OTA Update Full Package 6.6.28
http://bigota.d.miui.com/6.6.28/miui_MI3WMI4WAlphaGlobal_6.6.28_52f73ad90f_6.0.zip
OTA Update from 6.6.1 to 6.6.3 global alpha
http://bigota.d.miui.com/6.6.3/miui-ota-cancro_alpha_global-6.6.1-6.6.3-0991bbd15d-6.0.zip
OTA Update Full Package 6.6.3 global alpha
http://bigota.d.miui.com/6.6.3/miui_MI3WMI4WAlphaGlobal_6.6.3_020507d871_6.0.zip
6.6.3 eu_multi rom (unofficial global rom)
https://qc3.androidfilehost.com/dl/...81947/xiaomi.eu_multi_cancro_6.6.3_v8-6.0.zip
6.4.5 beta global : http://bigota.d.miui.com/6.4.5/miui_MI3WMI4WGlobal_6.4.5_09a48e7edd_6.0.zip
6.3.31>6.4.5 ota http://bigota.d.miui.com/6.4.5/miui-ota-cancro_global-6.3.31-6.4.5-f1389f749a-6.0.zip
6.3.31 beta global : http://bigota.d.miui.com/6.3.31/miui_MI3WMI4WGlobal_6.3.31_d234dcc6aa_6.0.zip
really nice
install gapps : https://drive.google.com/file/d/0B2UMSvqNe0deWFhRTGhJSEgyZ1k/view?usp=sharing
supersu- for rot :http://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
7.2.7 video: https://youtu.be/MAv8ekeueq8
Global 6.3.3 https://www.androidfilehost.com/?fid=24438995911970529
6.2.25 GLOBAL full : http://bigota.d.miui.com/6.2.25/miui_MI3WMI4WGlobal_6.2.25_41a7c373b2_6.0.zip
6.2.25 GLOBAL ota only for 6.2.23 : http://bigota.d.miui.com/6.2.25/miui-ota-cancro_global-6.2.23-6.2.25-18cf8540b2-6.0.zip
6.2.23 GLOBAL full : http://bigota.d.miui.com/6.2.23/miui_MI3WMI4WGlobal_6.2.23_19b11abf9d_6.0.zip
6.2.16 GLOBAL full : http://bigota.d.miui.com/6.2.16/miui_MI3WMI4WGlobal_6.2.16_4c58982281_6.0.zip
6.2.16 alpha full rom : http://bigota.d.miui.com/6.2.16/miui_MI3WMI4WAlpha_6.2.16_2590847604_6.0.zip
HOW TO INSTALL :
1. Flash Rom 5.12.17 with TWRP clean instal (wipe cache, dalvik, system ,data)(marshmallow need big partition --and 5.12.17 install for merge partition)
2. Reboot System
3. System setting-about phone > choose update packet( downloaded to the phone , select below rom)
6. Reboot To Recovery
7. Wipe User Data
8. Reboot System
9. Done
10. Good news open gapps working on 6.1.28-install and flash with twrp choose 6.0 and pico gapps
And needs may be - first aid box
1- OneClickRecovery - recovery video
2-İf u want back kitkat rom need two partittion special all.flash.bat
3-Google installer for china roms
4-BETA-SuperSU-v2.67 -- install video
FOLLOW ME ON YOUTUBE FOR ROM LINKS
Daily Beta or Alpha & gapps
6.1.28 GLOBAL FULL PACKET LINKS added on youtube 6.1.28 video
6.1.28 Develop-Global Version Full Root Rom
people said I should accept the world. Bull****! I don't accept the world.
RICHARD STALLMAN
Pls delete ur post. Say "No leaks!"
Thanks for sharing.... But move this thread to general section... Whoever want to try can try....its not against the XDA rules ....
do the alpha builds come on daily basis??
vinprivag said:
do the alpha builds come on daily basis??
Click to expand...
Click to collapse
Of course not. They are weekly or more than that as what I saw
Exiting..
Sent from my MI 3W using Tapatalk
29 is out
Dr. Ramm said:
29 is out
Click to expand...
Click to collapse
you have the link?
Dr. Ramm said:
29 is out
Click to expand...
Click to collapse
plz share link
I added a new rom 5.12.29
Thanks for sharing. You will add future links in future updates? :angel:
I have some issue of google contact sync and calendar sync. First time after install contact and calendar sync by google installer it work but after that it not sync.
murattiy said:
This rom for special beta tester use
AND CHANGE İN FLASH.BAT FİLES
Click to expand...
Click to collapse
I flashed this on Mi4 my device doesn't even start it doesn't even boot to FASTBOOT screen is simply not turning on
Prince Chandela said:
I flashed this on Mi4 my device doesn't even start it doesn't even boot to FASTBOOT screen is simply not turning on
Click to expand...
Click to collapse
pls sayme step tep
Prince Chandela said:
I flashed this on Mi4 my device doesn't even start it doesn't even boot to FASTBOOT screen is simply not turning on
Click to expand...
Click to collapse
check if your device in quhusb mode
ashish289 said:
check if your device in quhusb mode
Click to expand...
Click to collapse
murattiy said:
pls sayme step tep
Click to expand...
Click to collapse
I have an Idea to fix it I'm downloading fastboot Rom right now, it will take some time to download. (I'll report back here once I'm done downloading and Fixing) :good:
Meanwhile when I connect Mi4 to PC I see lots of drives 5-7 drives which are not accessible they need to be formatted. (I didn't do anything just left them as they are)
Prince Chandela said:
I have an Idea to fix it I'm downloading fastboot Rom right now, it will take some time to download. (I'll report back here once I'm done downloading and Fixing) :good:
Meanwhile when I connect Mi4 to PC I see lots of drives 5-7 drives which are not accessible they need to be formatted. (I didn't do anything just left them as they are)
Click to expand...
Click to collapse
Unbrick the mi3/4 like this. Follow the steps:
1) get a fastboot rom. Preferably miui 7 leaked Chinese version fastboot rom.
2) revert back to the dual partition using cwm recovery
3) Goto fastboot menu, connect to pc and using miflash tool flash the fastboot rom. Make sure flash_all.bat is selected in the advanced option.
4) it takes time for initial boot.
5) transfer the zip files of 5.12.17 version and latest 5.12.29 into the Phone Memory.
6)rename 5.12.29 zip to update.zip
7) open Updater app in miui - menu - choose update file and select 5.12.17.
8) 5.12.17 will merge the partition
9)after successful flashing reboot and goto recovery
10) clear cache and data
11) flash update.zip
I can not install the gapps. Any help?
ganeshrnet said:
Unbrick the mi3/4 like this. Follow the steps:
1) get a fastboot rom. Preferably miui 7 leaked Chinese version fastboot rom.
2) revert back to the dual partition using cwm recovery
3) Goto fastboot menu, connect to pc and using miflash tool flash the fastboot rom. Make sure flash_all.bat is selected in the advanced option. p
Click to expand...
Click to collapse
My screen doesn't turn on. How can i use CWM then?
---------- Post added at 04:58 PM ---------- Previous post was at 04:43 PM ----------
murattiy said:
pls sayme step tep
Click to expand...
Click to collapse
ashish289 said:
check if your device in quhusb mode
Click to expand...
Click to collapse
Hi, Now mi4 is not even getting detected as QHUSUB Bulk on PC
murattiy said:
I added a new rom 5.12.29
Click to expand...
Click to collapse
Exactly where do u get the links bro?
---------- Post added at 05:00 PM ---------- Previous post was at 04:58 PM ----------
Prince Chandela said:
My screen doesn't turn on. How can i use CWM then?
---------- Post added at 04:58 PM ---------- Previous post was at 04:43 PM ----------
Hi, Now mi4 is not even getting detected as QHUSB device?
Click to expand...
Click to collapse
Can you see the drives connected than?
I had the same problem you have (except I could properly see the device as QHSUB which ur saying now lost)
Just open MI Flash and check if you can see the device. If yes than simply flash any fastboot ROM
Hi guys !
I have aproblem with RMN4 (sd ) miui 8.1.15 , every time i flash TWRP i alway get freezing in MI logo and can't boot into system
any idea? please help me
Thanks !
i install this TWRP
https://forum.xda-developers.com/re...er-development/recovery-twrp-3-0-2-0-t3550061
lightcyan said:
Hi guys !
I have aproblem with RMN4 (sd ) miui 8.1.15 , every time i flash TWRP i alway get freezing in MI logo and can't boot into system
any idea? please help me
Thanks !
i install this TWRP
https://forum.xda-developers.com/re...er-development/recovery-twrp-3-0-2-0-t3550061
Click to expand...
Click to collapse
Did you tried
Fastboot boot <whatevertherecoveryname.img> once you done flashing twrp?
sachin n said:
Did you tried
Fastboot boot <whatevertherecoveryname.img> once you done flashing twrp?
Click to expand...
Click to collapse
yes : fastboot flash recovery twrp-3.1.0-0-mido.img
lightcyan said:
yes : fastboot flash recovery twrp-3.1.0-0-mido.img
Click to expand...
Click to collapse
After this command, do no reboot your phone, just keep your device connected then -
Fastboot boot <whatevertherecoveryname.img>, after this command wait few seconds, it'll boot to TWRP.
Once you get into recovery, flash lazyflasher.zip then reboot from twrp. If you won't flash lazyflasher, device wont boot.
sachin n said:
After this command, do no reboot your phone, just keep your device connected then -
Fastboot boot <whatevertherecoveryname.img>, after this command wait few seconds, it'll boot to TWRP.
Once you get into recovery, flash lazyflasher.zip then reboot from twrp. If you won't flash lazyflasher, device wont boot.
Click to expand...
Click to collapse
i did it but not work
lightcyan said:
i did it but not work
Click to expand...
Click to collapse
try this stable recovery
https://forum.xda-developers.com/re...r-development/twrp-twrp-3-1-0-0-mido-t3590814
if fails then unbrick your device from here
https://www.youtube.com/watch?v=7nzUbp732Ow
good luck
hit thumbs up if i helped you
lightcyan said:
i did it but not work
Click to expand...
Click to collapse
What rom are you on? Stable miui right?
---------- Post added at 09:17 ---------- Previous post was at 09:14 ----------
rony raj said:
try this stable recovery
https://forum.xda-developers.com/re...r-development/twrp-twrp-3-1-0-0-mido-t3590814
Click to expand...
Click to collapse
The one he's using is also stable recovery, you were just linked a themed one. Makes no sense.
Rony rai said:
if fails then unbrick your device from here
https://www.youtube.com/watch?v=7nzUbp732Ow
good luck
hit thumbs up if i helped you
Click to expand...
Click to collapse
This is ain't MTK, he's using an SD VERSION.
---------- Post added at 09:19 ---------- Previous post was at 09:17 ----------
@lightcyan, tell me what's your device's status now? Is that booting? Or looping? Or just pops Mi logo when you long press power button?
8.1.15 has problems with custom recovery. Update to 8.2.2 or 8.2.4. Then flash TWRP, Boot recovery and flash lazyflasher.
Gesendet von meinem Redmi Note 4 mit Tapatalk
Hi,
sorry if i'm the 100th person to ask this question but how can i go back to the stock ROM with OTA?
I currently have a flavor of LinageOS with the Turbo Z kernel installed on my phone but it's just to buggy for me. I want to have root access on my phone for various reasons though.
I tried to just download different (6.0/7.0) stock ROM files but i can't install them with TWRP. I know that 7.1.x was released but i can not find the ROM for it.
What is the easiest way to just go back to a stock ROM? I know my way around the console but i don't want to brick my phone. I made backups of my files and also with TWRP so data loss is not an issue.
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
First things first.
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Use the fastboot flash / erase commands, as in this thread:
https://forum.xda-developers.com/showpost.php?p=73119650&postcount=1
If at any stage your phone get bricked, ie, black screen after reboot, no charging, etc. Use these instructions. They saved me in the last week from returning my device for a replacement(and paying $350.00):
https://forum.xda-developers.com/showpost.php?p=71874880&postcount=1
lollyjay said:
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Click to expand...
Click to collapse
Does this work for the EU version too? I'm not sure if the baseband thingy is compatible. I'll need a EU ROM otherwise but i can't find any for Android 7 :/
bert269 said:
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Click to expand...
Click to collapse
I've already updated to Android 7 so i guess i've to use a stock Nougat ROM.
Read my last post on page 15 of this thread
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113/page15
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
If you didn't take a backup of your stock boot and recovery before, then i think you'll have to go the long way by flashing the whole rom.
If you manage to install the 7.1.1 OTA after that, boot once into TWRP, backup stock recovery & boot and save it on your sdcard/pc. Then you can start flashing TWRP permantly, root, etc
Someone correct me, if I'm wrong.
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
What is your build number?
lollyjay said:
What is your build number?
Click to expand...
Click to collapse
The current build number is NPLS25.86-30-12
Byte_76 said:
The current build number is NPLS25.86-30-12
Click to expand...
Click to collapse
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Byte_76 said:
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Click to expand...
Click to collapse
You must have fully stock. I would suggest that you uninstall Magisk
lollyjay said:
You must have fully stock. I would suggest that you uninstall Magisk
Click to expand...
Click to collapse
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Byte_76 said:
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Click to expand...
Click to collapse
I still would suggest that you uninstall Magisk because the OTA would not work.
lollyjay said:
I still would suggest that you uninstall Magisk because the OTA would not work.
Click to expand...
Click to collapse
Okay I uninstalled Magisk which initiated an immediate reboot and resulted in a bootloop just after the bootloader message.
I think the issue occurs because the Data partition gets encrypted when root is uninstalled and decrpyption fails because of a bad key due to the unlocked bootloader.
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption. I then ran "fastboot continue" after which my phone booted back into Android:
https://forum.xda-developers.com/moto-z/help/bricked-moto-z-unlocking-bootlader-t3634701
My phone status was then: Stock Android 7.0.0, no_verity patch (no encryption), stock recovery, unlocked bootloader.
So my phone is about as close to stock as I can get it with unlocked bootloader.
I finally attempted to install the 7.1.1 OTA again. It reboots and indicates that it is installing and then pops up with a message that says "Error".
Pressing the power and up button brings up the recovery screen with the error log (with info that I don't understand) and from there I can reboot into system again where I get another message indicating that the update failed and no changes were made.
I'm hesitant to install RETBR or other non-RETEU roms (Because although they might work, there probably are some differences such as LTE bands etc. and they are not actually correct for my phone) so I'm not sure how else to get to 7.1.1 unless the wifi issue is resolved with the image that Erfanoabdi uploaded in another thread or Lenovo releases an official 7.1.1 firmware package for the RETEU model.
Byte_76 said:
.....
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption.........
Click to expand...
Click to collapse
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
bert269 said:
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
Click to expand...
Click to collapse
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Byte_76 said:
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Click to expand...
Click to collapse
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
Are these the commands that I should run?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
It's out of my knowledge if your verity patch influences either bootloader or gpt partition. So i would recommend to flash those two commands in order to "repair" them. If you'll get an error message, skip them and proceed with the rest.
I always prefer RSD method instead of manually flashing by fastboot commands.
Have you installed the latest version of RSD-lite 6.2.4? Have you installed the latest moto drivers?
If you have extracted the RETBR. zip, search for "flashall.xml" file. Open it with a texteditor and you'll find the correct flashing commands.
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
34.3.A.0.244 - 7.1.1 - 09 NOV 2017 update
F5122 IS AT https://mega.nz/#F!DEQykYjL!Vux2m1_Rug9hg9B4_q0ifw
F5121 .. https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ (THANKs @eagleeyetom )
both f5121/5122 folders have 1 kernel image,
FLASH THE ROM
FLASH THE KERNEL,
FLASH TWRP,
BOOT IN TO TWRP .
FLASH MAGISK or SUPERSU, VIA FLASHABLE ZIP
BOOT THE DEVICE
IF YOU HAVE FLASHED MAGIK THEN INSTALL MAGIS MANAGER
MAGISK POST https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
CHAINFIRE SUPERSU ZIPs LATEST AT https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
PREVIOUS KERNELS
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
https://forum.xda-developers.com/xperia-x/development/rooted-kernels-f5121-f5122-34-3-0-238-t3683968
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
https://forum.xda-developers.com/xp...ted-kernels-f5121-f5122-34-3-0-224-8-t3669793
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5121-f5122-34-3-0-217-7-t3654368
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
siggi77 said:
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
Click to expand...
Click to collapse
on https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ
the F5121_34.3.A.0.244_su.img is the kernel
just flash and your device will wakup ROOTED.
twrp 3.1.1 problem
on my 64 GB xperia X F5122
1. after flashing ROM if
2. I flash twrp 3.1.1 it will
3. make my system partition 40GB and i get only 20gb workable
I tried many things but flashing recovery via adb always create this problem and if i BOOT the device before going in to the partition , sony stockrom makes internal storage encrypted which then twrp3.1.1 is unable to read
plz help
@serajr @shoey63 @munjeni
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
siggi77 said:
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
Click to expand...
Click to collapse
i am sorry,
i have fixed it
please check again
thank you
Hi, great
thx for the new package
Siggi
clean kernel image is drm fixed??
kloroform said:
clean kernel image is drm fixed??
Click to expand...
Click to collapse
yes sir, it is,
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
xxarigattoxx said:
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
Click to expand...
Click to collapse
the guide is here
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
also twrp3.1.1 works best at 32gb variant by giving 20gb workable and putting systemparittion to 12gb
however it does the SAME with 46gb variant and give only 20gb workable and put system partition 40 gb
thats why for 64gb variants i don't recomend using twrp3.1.1
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Jomoteck said:
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Click to expand...
Click to collapse
once you flash the modified kernel with supersu then there is no need for twrp, simply boot your device and it will wakeup rooted.
however if you wana use magisk and your device is 64gb then i highly recommend you to do this
1. flash rom
2. flash the modified kernel
3. boot the device and go thru sony setup , give google account and let it sync
4. switch off mobile after 15 or so mins
5. flash twrp3.1.1 suzu (given in the mega link, in the OT)
6. HOLD power and VOLUME DOWN BUTTON till PINK led comes on sonylogo and you are taken to twrp, keep system readonly and flash magisk ( via otg or if you had it in your sd card prior) ( at this point you may flash other zips also, if there are any)
7. twrp may give you error such as... cannot mount internal storage etc, just ignore.
8. after flashing, switchoff mobile, and boot it into system.
9. for safty purposes, you can erase twrp by connecting device in fastboot mode and executing following command
Code:
fastboot erase recovery
now you can ask me why i let you boot your device first. normally its unprecedented.
the reason i explain here
https://forum.xda-developers.com/showpost.php?p=74573987&postcount=121
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
nova001 said:
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
Click to expand...
Click to collapse
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
YasuHamed said:
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
Click to expand...
Click to collapse
thats oke, but we cant dowload anywhere? only xperifirm ?
nova001 said:
thats oke, but we cant dowload anywhere? only xperifirm ?
Click to expand...
Click to collapse
Xperifirm is the best
Other servers i cant guarantee
I was able to flash rom, flash kernel, flash root and boot the phone and was able to use it.
PROBLEM:
- It heats up during use.(FIXED) constant mobile data was the cause..
- Everytime I lock the screen my mobile data turns on when I unlock the SCREEN. (FIXED) disable find my device as administrator.
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
cyanides13 said:
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
Click to expand...
Click to collapse
Yes it works I use it actually.
hi
after flash new rom , bootloop 1 sec
the phone reboot to logo and make reboots every 1 sec
if i try to boot to fast boot i will see the fast boot logo for 1 sec and the phone reboot again
flashtool not working, in this case fastboot cmd not working
any help ??
pokernet said:
hi
after flash new rom , bootloop 1 sec
the phone reboot to logo and make reboots every 1 sec
if i try to boot to fast boot i will see the fast boot logo for 1 sec and the phone reboot again
flashtool not working, in this case fastboot cmd not working
any help ??
Click to expand...
Click to collapse
Had you unlocked the bootloader? what rom had you flashed?
Sent from my U65GT using Tapatalk
papatzis said:
Had you unlocked the bootloader? what rom had you flashed?
Sent from my U65GT using Tapatalk
Click to expand...
Click to collapse
yes i unlock bootloader and install twrp bootloader
the problem i cnot get to the twrp and cnot get to fastboot,
i flash the rom with twrp, all go ok, after the reboot the phone start make restart and not loading ...
fastboot showing for 1sec and then reboot
twrp not loading !
rom : miui_CURTANAINGlobal_V11.0.4.0.QJWINXM_5c420fbe36_10.0.zip
as i understand i need to make EDL mode but i dont know howto make it .
pokernet said:
yes i unlock bootloader and install twrp bootloader
the problem i cnot get to the twrp and cnot get to fastboot,
i flash the rom with twrp, all go ok, after the reboot the phone start make restart and not loading ...
fastboot showing for 1sec and then reboot
twrp not loading !
rom : miui_CURTANAINGlobal_V11.0.4.0.QJWINXM_5c420fbe36_10.0.zip
as i understand i need to make EDL mode but i dont know howto make it .
Click to expand...
Click to collapse
I am pretty sure you flashed via twrp without format data first.
reinstall twrp and proceed as normal. format data in twrp wipe section.
As I understood he cannot do that because either twrp or fastboot don't stay but reboot immediately.
Concerning file explorers it is not the root permissions that triggers the problem, BUT IF YOU ADD OR CORRECT SOMETHING IN SYSTEM PARTITION.
Στάλθηκε από το Redmi Note 4 μου χρησιμοποιώντας Tapatalk
pokernet said:
hi
after flash new rom , bootloop 1 sec
the phone reboot to logo and make reboots every 1 sec
if i try to boot to fast boot i will see the fast boot logo for 1 sec and the phone reboot again
flashtool not working, in this case fastboot cmd not working
any help ??
Click to expand...
Click to collapse
You can try 2 methods to enter EDL mode and recover the phone. The first is to use a USB cable and create a bridge by joining the green cable (positive data) with the black (GND or negative), then you try to glaze with the Miflash tool, in theory you should recognize it in that mode. In the second method you must uncover the phone and use the test points above of the battery and create a Bridge with a metalic object in orden to enter un the EDL Mode.
papatzis said:
As I understood he cannot do that because either twrp or fastboot don't stay but reboot immediately.
Concerning file explorers it is not the root permissions that triggers the problem, BUT IF YOU ADD OR CORRECT SOMETHING IN SYSTEM PARTITION.
Στάλθηκε από το Redmi Note 4 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I have successfully changed the hosts file with my own file in system/etc.
This is system partition? right.
Done on 11.05eu and on twrp installed 11.08eu with X-plore file manager. (should be same with other FM)
Disabled root after modification done. still Magisk installed.
It is matter of testing, don't ask me to make more modification..... until issue is fixed or well understood.
---------- Post added at 01:17 AM ---------- Previous post was at 01:12 AM ----------
migue daza said:
You can try 2 methods to enter EDL mode and recover the phone. The first is to use a USB cable and create a bridge by joining the green cable (positive data) with the black (GND or negative), then you try to glaze with the Miflash tool, in theory you should recognize it in that mode. In the second method you must uncover the phone and use the test points above of the battery and create a Bridge with a metalic object in orden to enter un the EDL Mode.
Click to expand...
Click to collapse
You are late!
this was valid during last EDL war some years ago...
---------- Post added at 01:22 AM ---------- Previous post was at 01:17 AM ----------
pokernet said:
hi
after flash new rom , bootloop 1 sec
the phone reboot to logo and make reboots every 1 sec
if i try to boot to fast boot i will see the fast boot logo for 1 sec and the phone reboot again
flashtool not working, in this case fastboot cmd not working
any help ??
Click to expand...
Click to collapse
Use Miflash tool and a fastboot rom if you can't get back TWRP
Same problem here. Did you have any solution if yes, how did you fix the phone?
I faced the problem too with my redmi note 9 pro global..before it i succeed with unlocking the bootloader, flashing unofficial twrp, rooting the device with magisk..but when i tried to flashing with xiaomi.eu rom the problem came out..tried to power on the device but it just show problem with 1 sec with the redmi log & 1 sec with fastboot logo..
I have tried to reflashing with the original global rom using miflash & also qpst but still failed..
Need a solution ASAP:crying:
---------- Post added at 03:38 AM ---------- Previous post was at 03:34 AM ----------
lolo9393 said:
I have successfully changed the hosts file with my own file in system/etc.
This is system partition? right.
Done on 11.05eu and on twrp installed 11.08eu with X-plore file manager. (should be same with other FM)
Disabled root after modification done. still Magisk installed.
It is matter of testing, don't ask me to make more modification..... until issue is fixed or well understood.
---------- Post added at 01:17 AM ---------- Previous post was at 01:12 AM ----------
You are late!
this was valid during last EDL war some years ago...
---------- Post added at 01:22 AM ---------- Previous post was at 01:17 AM ----------
Use Miflash tool and a fastboot rom if you can't get back TWRP
Click to expand...
Click to collapse
You need an authorized mi account to do that but now xiaomi has restricted to give authorization to new mi account..in other word, flashing using miflash is useless now except if you can patching the prog_ufs_firehouse_sm6250.elf to bypass the mi authentication..
getsuga92 said:
I faced the problem too with my redmi note 9 pro global..before it i succeed with unlocking the bootloader, flashing unofficial twrp, rooting the device with magisk..but when i tried to flashing with xiaomi.eu rom the problem came out..tried to power on the device but it just show problem with 1 sec with the redmi log & 1 sec with fastboot logo..
I have tried to reflashing with the original global rom using miflash & also qpst but still failed..
Need a solution ASAP:crying:
I have the same problem, if you find out how to fix it tell me to do it, thanks
Click to expand...
Click to collapse
alshoc said:
getsuga92 said:
I faced the problem too with my redmi note 9 pro global..before it i succeed with unlocking the bootloader, flashing unofficial twrp, rooting the device with magisk..but when i tried to flashing with xiaomi.eu rom the problem came out..tried to power on the device but it just show problem with 1 sec with the redmi log & 1 sec with fastboot logo..
I have tried to reflashing with the original global rom using miflash & also qpst but still failed..
Need a solution ASAP:crying:
I have the same problem, if you find out how to fix it tell me to do it, thanks
Click to expand...
Click to collapse
---------- Post added at 01:00 PM ---------- Previous post was at 12:51 PM ----------
Till now never ever flashing any rom to any redmi note 9 pro using twrp till officially release to risky lead to hard brick, better using fastboot to flashing device for now, after unlock bootloader, my experience i can use any official rom swiching to QJZEU, QJZMI, QJZID without any issue or hard brick
Click to expand...
Click to collapse
hendibudi said:
alshoc said:
---------- Post added at 01:00 PM ---------- Previous post was at 12:51 PM ----------
Till now never ever flashing any rom to any redmi note 9 pro using twrp till officially release to risky lead to hard brick, better using fastboot to flashing device for now, after unlock bootloader, my experience i can use any official rom swiching to QJZEU, QJZMI, QJZID without any issue or hard brick
Click to expand...
Click to collapse
What software tool do you use?
Click to expand...
Click to collapse
getsuga92 said:
hendibudi said:
What software tool do you use?
Click to expand...
Click to collapse
Official rom for fastboot flashing already included just unzip and flashing
here the link for redmi note 9 pro https://mirom.ezbox.idv.tw/en/phone/joyeuse/
Click to expand...
Click to collapse
BootLoop
hendibudi said:
getsuga92 said:
Official rom for fastboot flashing already included just unzip and flashing
here the link for redmi note 9 pro https://mirom.ezbox.idv.tw/en/phone/joyeuse/
Click to expand...
Click to collapse
Hy, any solution for this issue? (bootloop)
Thx
Click to expand...
Click to collapse
ovbu77 said:
hendibudi said:
Hy, any solution for this issue? (bootloop)
Thx
Click to expand...
Click to collapse
If bootloop, just reflash using mi flash with official rom on fastboot mode..
If hardbrick, no solution yet..send the device to mi center to fix it
Click to expand...
Click to collapse
is there any solution about it
after miui eu installation my phone gone . it bootloops
there is no fastboot mode.
i installed fastboot rom with someone s authorised id but it loops again. what must i do
ilkerxxx said:
is there any solution about it
after miui eu installation my phone gone . it bootloops
there is no fastboot mode.
i installed fastboot rom with someone s authorised id but it loops again. what must i do
Click to expand...
Click to collapse
What is the codename of device you have? Curtana or Joyeuse?
You guys are probably confusing both devices as One and flashing wrong ROM zips that leads to hard bricks.
goldenevil47 said:
What is the codename of device you have? Curtana or Joyeuse?
You guys are probably confusing both devices as One and flashing wrong ROM zips that leads to hard bricks.
Click to expand...
Click to collapse
Yeah..mostly because of it
Afterall, all xiaomi phone are suckk..
Why not have they just sell only one variant to all of country..why'd they use the same global name for 2 different codename of phone..
I don't understand..
getsuga92 said:
Yeah..mostly because of it
Afterall, all xiaomi phone are suckk..
Why not have they just sell only one variant to all of country..why'd they use the same global name for 2 different codename of phone..
I don't understand..
Click to expand...
Click to collapse
Yes there's issues with naming system but that's where codename comes in, right? Why can't people just read probably ?
I have the same problem. Installed xiaomi.eu rom verison 11.04, tried to update to 10.11 and stuck. What can cause that? I did exactly what they asked me to: formatted the /data partition (ONLY), installed via TWRP.
First time trying modified rom, it's a very bad experience and very time consuming. Probably won't ever going to do that again. :|