yes! i flashed by updater, then i wiped cache, dalvik and dataSorry I don't use bluetooth myself. Did you flash with wipe already?
yes! i flashed by updater, then i wiped cache, dalvik and dataSorry I don't use bluetooth myself. Did you flash with wipe already?
China dev 6.4.2.1 and global stable 7.2.4.0 have the same problem! I've tried...Just as a matter of interest , do the 'bugs '/problems that users encounter pre-exist in the China dev rom , or do they occur as a consequence of xiaomi.eu actions ?
all new updates are android 6 that implies system new partitions.hello,
for this update does my mi4 needs to run on android 6.0 because for the moment he is running on andriod 4.4.4
Hey guys,
Total noob here (both in the forums and to the Xiaomi landscapes). I must say this community and its rom seem promising!
I have, just now, hardbricked my Redmi Note 3 Pro (Kenzo) for the second time.
I've done a test point to revive it the first time after I carelessly flashed a stock MIUI rom from TWRP after being unhappy with an AOSP rom for this device. All was well in the end and I had a stock device with a stock MIUI rom (bootloader locked).
Just about a half hour ago I succesfully re-unlocked the bootloader again the unofficial way.
I download both the Kenzo's TWRP and rom as found in the OP but sadly was unable to flash the TWRP package through the updater app in MIUI (error shown: Couldn't verify zip package). I therefore booted into fastboot mode to flash it through windows cmd.exe after which I booted into TWRP.
From there I followed the instructions, or so I believe, and just flashed the Xiaomi.eu Kenzo rom from this thread. When all was done I was prompted with the question if I wanted to install SU in order to gain root access. I thought "nah, the rom is pre-rooted, I'm good..."
After rebooting the phone is dead/hardbricked yet again, and performing another test point resurrection seems like the only way of reviving the damn thing once again.
Can anyone point me where I've gone wrong? Is the rom bound to the specific TWRP package posted in this thread? Could this have all been prevented if I simply accepted TWRP's request of rooting the phone after flashing the rom? Does this only work after my phone has official approval of having an unlocked bootloader?
Cliffs/tl;dr:
1. Unlocked bootloader (unofficial way)
2. TWRP zip wouldn't flash through updater (Couldn't verify zip package)
3. Flashed TWRP.img (from TWRP's official site) through fastboot commands using windows cmd.exe
4. Entered recovery, flashed xiaomi.eu rom
5. Didn't root the phone when prompted by TWRP
6. Upon rebooting, phone momentarily shows MI logo and shuts down (hardbricked)
7. How to proceed after reviving my phone?
Thank you in advance for your help, it is much appreciated!
I also hope 7.3.3, in the meantime stable 7.3.2 is very good.Hello. What is the best firmware for MI3 on 6 Android for now? I tried the last weekly and my phone sometimes loses bluetooth connect with miband (all permissions and options are on). Also the battery drain i so creepy... May be there is the better old version?
Or stable? By the way, will the 7.3.3.0 be posted?
You can reboot to recovery by opening updater app and clicking on the three dotsCan you please add Reboot to recovery in the power options??
Dont worry, Gaps dont work well too. Install latest 4.4.
Install 5.12.17 twice via updater app, flash twrp, flash latest rom.hello,
for this update does my mi4 needs to run on android 6.0 because for the moment he is running on andriod 4.4.4
Use flashify or flash 6.2.25 rom.Cant install WTRP on my Redmi 3
I tried with updater [couldn't verify update package] and flashboot but still not working...
Upgraded to 5.12.17 TWICE?hi, i'm new to all of this, trying to install this rom to get dutch language. but when i install it on my mi4 lte i get an error in twrp saying mount: no partition named "/dev/block/platform/msm_sdcc.1/by-name/userdata" and after that, failed to extract system to /system and error 7 at the end. to be sure i did download 5.x and upgraded to 5.12..17 to be sure it had the merged partitions, but still doesn't work.
Do you have a battery drain on Leo with this ROM ?
Envoyé de mon MI NOTE Pro en utilisant Tapatalk
Hi mate,
If you want to use unofficial unlock method you will need cracked boot.img every time you flash MIUI ROM or when installing TWRP.
Otherwise you'll get boot loop!
My suggestion is to unlock devise officially.
Regards!
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation