Fastboot rom install with
-miflashtool
6.6.3 GLOBAL Official Alpha Fastboot rom
6.6.3 eu_multi -Unofficial Global rom (install with twrp revovery )
6.6.3 china twrp alpha rom
6.5.31 fastboot rom Download
miui7
6.5.30 Global fastboot rom
6.5.30 Global TWRP rom
7.2.9 Global Stable Fastboot Rom
6.5.20 Global TWRP Beta Rom
install with TWRP (please dont try with system updates>choose packet)
murattiy said:
6.5.20 global beta
https://drive.google.com/file/d/0B2UMSvqNe0deY0h3YW1aX20wdDQ/view?usp=sharing
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
Where did you take it? There is no post in xiaomi official forum. And how to install it over 7.2.4 global?
Thanks
murattiy said:
6.5.20 global beta
https://drive.google.com/file/d/0B2UMSvqNe0deY0h3YW1aX20wdDQ/view?usp=sharing
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
There is also a official URL: http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
---------- Post added at 13:37 ---------- Previous post was at 13:35 ----------
giardux91 said:
Where did you take it? There is no post in xiaomi official forum. And how to install it over 7.2.4 global?
Thanks
Click to expand...
Click to collapse
It should be flashable in fastboot mode or at least in EDL mode with the latest MiuiFlash.
shade.sh said:
There is also a official URL: http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
---------- Post added at 13:37 ---------- Previous post was at 13:35 ----------
It should be flashable in fastboot mode or at least in EDL mode with the latest MiuiFlash.
Click to expand...
Click to collapse
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
giardux91 said:
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
Click to expand...
Click to collapse
You're right... looks like a OTA or something image... i don't have my Mi5 with me to check if you can flash it via TWRP.
shade.sh said:
You're right... looks like a OTA or something image... i don't have my Mi5 with me to check if you can flash it via TWRP.
Click to expand...
Click to collapse
The strange thing is that this rom doesn't exist on xiaomi forum.
giardux91 said:
The strange thing is that this rom doesn't exist on xiaomi forum.
Click to expand...
Click to collapse
There was a thread in the English forum, but was deleted very quick:
http://webcache.googleusercontent.c...94-1-1.html&gws_rd=cr&ei=JaFBV5alFIX7UpfbgOgE
shade.sh said:
There was a thread in the English forum, but was deleted very quick:
http://webcache.googleusercontent.c...94-1-1.html&gws_rd=cr&ei=JaFBV5alFIX7UpfbgOgE
Click to expand...
Click to collapse
I think it's not safe to install it, what do you think about?
giardux91 said:
I think it's not safe to install it, what do you think about?
Click to expand...
Click to collapse
Well, i never had it installed, so i cannot say anything about it... maybe the thread starter could say something about it
We only know its not "official" available.
I flashed it and am using it since yesterday. So far I haven't encountered any issues but I'm kind of put off by the state of their ROMs for this phone currently and hence haven't exactly 'tested' anything out.
The thread on the Chinese forum is still alive but they aren't letting people post it International apparently.
http://www.miui.com/thread-4296538-1-1.html
In case anyone needs info how to install it -> installed it via Updater which brings you to TWRP, after which the devices was decrypting and after it installed as any other update. Took about 20mins. Installed it "over" xiaomi.eu_multi_gemini_6.5.19_v7-6.0.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"
}
This rom rewrites recovery to the stock one and decrypts data. I re-flashed twrp recovery but in twrp it asks me for password to access/decrypt the data (the data thats on the phone, such as TWRP backups and other ROM .zip's) ? I have no lock screen/no password on my phone. Tried booting in system and setting lock screen password and using that in TWRP but no luck. Tried "default password" but it does not work. I wan't to restore other version of en.miui rom, but I can't access it via TWRP now. Any ideas for the password or way around? I am too lazy to reflash MiFLash version of 6.4.21 and then copy my TWRP backups onto the phone..
jemeljsh said:
This rom rewrites recovery to the stock one and decrypts data. I re-flashed twrp recovery but in twrp it asks me for password to access/decrypt the data (the data thats on the phone, such as TWRP backups and other ROM .zip's) ? I have no lock screen/no password on my phone. Tried booting in system and setting lock screen password and using that in TWRP but no luck. Tried "default password" but it does not work. I wan't to restore other version of en.miui rom, but I can't access it via TWRP now. Any ideas for the password or way around? I am too lazy to reflash MiFLash version of 6.4.21 and then copy my TWRP backups onto the phone..
Click to expand...
Click to collapse
Check over at the MIUI forums, I think someone mentioned this issue and how to fix it. I have locked bootloader so no experience with TWRP on this phone yet.
murattiy said:
6.5.20 global beta
official rom but boot error official rom rom .official rom link : http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
my link diffirent and working rom.(changed boot.img)
https://drive.google.com/open?id=0B2UMSvqNe0deU0ZkRHcxNUdFMkE
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
Surprisingly original one works through updater. But in the yesterday morning when nI tried via TWRP it does not worked for me and showed boot.img related error but flashed successfully and device never booted up and stuck on boot logo. Then I flashed 7.2.4.0 again and just for checking I tried to flash manually via updater apps and it works. Unlike other updater ROM this one wiped all data (though I did not have any) and had a clean install.
kamrul.auntu said:
Surprisingly original one works through updater. But in the yesterday morning when nI tried via TWRP it does not worked for me and showed boot.img related error but flashed successfully and device never booted up and stuck on boot logo. Then I flashed 7.2.4.0 again and just for checking I tried to flash manually via updater apps and it works. Unlike other updater ROM this one wiped all data (though I did not have any) and had a clean install.
Click to expand...
Click to collapse
this doesn't look like a fastboot ROM!
Just to add details:
Xiaomi names fastboot Roms with "phone_name"_"version"...
like the Mi5 fastboot Roms are: gemini_images_V....
And Mi5 Recovery ROms are miui_MI5...
So if you tried to flash it as a fastboot ROM it's likely to not work.
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
giardux91 said:
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
Click to expand...
Click to collapse
I had the similar message when going from 7.3.3.0 China to the latest China developer. I would not mind it.
SavageDamage said:
Check over at the MIUI forums, I think someone mentioned this issue and how to fix it. I have locked bootloader so no experience with TWRP on this phone yet.
Click to expand...
Click to collapse
I could not find the solution to get back to 6.5.19 eu.miui rom. Whatever password options I tried within TWRP data would not unlock/decrypt (tried -> password, default_password, default password, "lock screen password/lock screen pin").
To resolve the issue I:
1. copied contents (including made backups with TWRP 3.0.2) of the phone while booted into the system to my pc 2. reflashed MiFLash version of 6.4.21 eu.miui rom via MiFlash in FastBoot;
3. reflashed TWRP to the one version which matched the version of my TWRP backups (3.0.2)
4. while booted into 6.4.21 eu.miui rom copied TWRP backup from pc to the phone
5. booted into TWRP and restored my TWRP backup.
So the test of this rom version costed my 2 hours :laugh:
TheUltrametricSpace said:
this doesn't look like a fastboot ROM!
Just to add details:
Xiaomi names fastboot Roms with "phone_name"_"version"...
like the Mi5 fastboot Roms are: gemini_images_V....
And Mi5 Recovery ROms are miui_MI5...
So if you tried to flash it as a fastboot ROM it's likely to not work.
Click to expand...
Click to collapse
@TheUltrametricSpace
I never told that it looks like a fastboot ROM kind of a thing! Looking at the inside of zip file also can indicate that which one fastboot or which one is recovery ROM. BTW, I am still waiting for your comment on another of mine thread where I mentioned you. This is, I am not getting mobile network signal most of the times and get it back network barely. Impossible to use the phone. Please help.
I was just trying to say OP that original one (leaked) worked for me through phone updater rather TWRP. TWRP can flash it but firmware don't have ability to boot the device. That is why I 1st rollback to to Global stable 7.2.4.0 and then update this ROM. Even not seen any verification error in the flashing process. But TWRP presented me error in boot.image which OP mentioned. I think this ROM leaked from any closed alpha/beta tester and that is why updater apps not shows any error. If you try to install 7.2.8.0 over 7.2.4.0 recovery ROM it shows verification error.
kamrul.auntu said:
@TheUltrametricSpace
I never told that it looks like a fastboot ROM kind of a thing! Looking at the inside of zip file also can indicate that which one fastboot or which one is recovery ROM. BTW, I am still waiting for your comment on another of mine thread where I mentioned you. This is, I am not getting mobile network signal most of the times and get it back network barely. Impossible to use the phone. Please help.
I was just trying to say OP that original one (leaked) worked for me through phone updater rather TWRP. TWRP can flash it but firmware don't have ability to boot the device. That is why I 1st rollback to to Global stable 7.2.4.0 and then update this ROM. Even not seen any verification error in the flashing process. But TWRP presented me error in boot.image which OP mentioned. I think this ROM leaked from any closed alpha/beta tester and that is why updater apps not shows any error. If you try to install 7.2.8.0 over 7.2.4.0 recovery ROM it shows verification error.
Click to expand...
Click to collapse
ja ja, i wrote this in general. Sorry.
Dunno about the other parts you wrote sorry.
Has anyone tried Global Stable 7.2.9?
Is it possible install ufficial rom over xiaomi.eu rom?
Related
I have combined the OnePlus 3 and OnePlus 3T TWRP threads into a single thread for the unified build.
Please visit:
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
I apologize for the inconvenience.
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3T, Tool/Utility for the OnePlus 3T
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3t
Version Information
Status: Stable
Current Stable Version: 3.0.3-1
Stable Release Date: 2017-01-16
Created 2016-11-26
Last Updated 2017-01-22
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
ghettopops said:
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
Click to expand...
Click to collapse
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
jcadduono said:
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
Click to expand...
Click to collapse
So that means it doesn't use that new layout which includes dual A/B partitions right? If the only benefit of dual partitions is seamless updates, I guess the traditional layout is fine or even better.
Edit: Both this TWRP thread and the Tyranus kernel thread came out pretty quick, and seem very well documented and professional compared to some of the other Non Nexus device threads. I'm impressed. I just hope the threads stay uncluttered. Thank you.
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
someone0 said:
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
Click to expand...
Click to collapse
Done. Should now default to f2fs on data wipes as well. (redownload, I didn't change the version number)
Yes that is an option.
ghettopops said:
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Click to expand...
Click to collapse
No, separate recovery partition means you can flash kernels and recoveries separately. It means recovery isn't part of the system boot image, which is an idiotic design of the Pixel phones that is hurting custom development for them. See example:
OnePlus 3T (and every other sane device):
boot partition = system boot image
recovery partition = recovery boot image
result = you can use twrp to flash custom roms! any issues = just try in twrp again!
Pixel:
boot partition = boot image with recovery ramdisk that loads system (???)
boot_a partition = the same thing as boot partition (??? again)
recovery partition = nowhere to be found
result = flash a bad custom rom? say goodbye to twrp!
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
charlieb620 said:
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
Click to expand...
Click to collapse
need recovery.log ... i'm guessing this is happening due to changing default partition type for data from ext4 to f2fs, might need to change it back
in the meantime, setting default back to ext4....redownload (again)
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
jcadduono said:
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Click to expand...
Click to collapse
Woah! Now official nethunter? I can test this Monday when I get the device. I would be surprised if we got copperhead OS too.
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
charlieb620 said:
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
Click to expand...
Click to collapse
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
someone0 said:
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
Click to expand...
Click to collapse
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
jcadduono said:
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
Click to expand...
Click to collapse
{
"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"
}
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
charlieb620 said:
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
Click to expand...
Click to collapse
That screenshot seem like somebody is trying to run adb from within the android shell. I would just
'adb shell'
'su'
'cd /sdcard' or /tmp or whichever directory that's writable.
then run whatever command you need from there. Having another DOS windows open up is also a good idea. That way, one window is always running shell, and another is just DOS. so no confusion and no need to keep exiting shelf and get back in.
Fails to decrypt data. Here is logs from 3t 128gb model.
Black screen
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
hawki said:
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
Click to expand...
Click to collapse
How did you get root (superSU) installed w/o twrp?
BTW, you may have the same problem I had earlier, which is the stock OS is on version 3.5.1. You need to follow the instruction again, and flash recovery and boot into twrp.img After that, patch your OS to the latest via OTA, I think you need to re-root again after that.
just to be clear. Since I am already rooted am I just flashing twrp and swiping for Mods?
This is the LeEco Le Pro 3's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
I didn't try it yet
But Thank you for your work,
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
It is compatible for the lepro3? I used it before for oneplus2.
meuhmeuh51 said:
It is compatible for the lepro3? I used it before for oneplus2.
Click to expand...
Click to collapse
Yes, it's completely compatible, i have tested it on my leeco le pro 3
mauronofrio said:
Yes, it's completely compatible, i have tested it on my leeco le pro 3
Click to expand...
Click to collapse
ok I will try
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently
Sent from my SM-P600 using XDA-Developers Legacy app
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently<br />
<br />
Sent from my SM-P600 using XDA-Developers Legacy app
Sent from my LEX727 using XDA-Developers Legacy app
toanau said:
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently<br />
<br />
Sent from my SM-P600 using XDA-Developers Legacy app
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
no
Think I just bricked my Le Eco Pro 3. Dragged the ROM into the root system of my X727 I was going to flash, Lineage 13
Enabled USB Debug
Unlocked Bootloader
Flashed GS Custom Recovery
Wiped Everything
Went to Flash the ROM, and nothing showed up...
I rebooted, and now I think the stock recovery re-installed itself, and there is no ROM present because I wiped everything.
Help
I just get a flicker of the Le Eco Boot Screen, then it shuts off. Can't get into ADB or Recovery.
kaivorth said:
Think I just bricked my Le Eco Pro 3. Dragged the ROM into the root system of my X727 I was going to flash, Lineage 13
Enabled USB Debug
Unlocked Bootloader
Flashed GS Custom Recovery
Wiped Everything
Went to Flash the ROM, and nothing showed up...
I rebooted, and now I think the stock recovery re-installed itself, and there is no ROM present because I wiped everything.
Help
I just get a flicker of the Le Eco Boot Screen, then it shuts off. Can't get into ADB or Recovery.
Click to expand...
Click to collapse
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
coolmaster121 said:
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
Thankfully I fixed it.
Flashed an aboot file, and all a sudden, Lineage 13 started up. You cannot believe how psyched I was. I was on eBay looking at my next phone, and all angry that I messed up my perfectly good phone.
I don't think this tool had anything to do with it. I was unforunate enough to wipe my phone before I went to install the ROM, and it wiped the ROM too. When it restarted, it had nothing to boot too. Just used Fastboot to flash the aboot file, and sideloaded the ROM and flashed away
kaivorth said:
Thankfully I fixed it.
Flashed an aboot file, and all a sudden, Lineage 13 started up. You cannot believe how psyched I was. I was on eBay looking at my next phone, and all angry that I messed up my perfectly good phone.
I don't think this tool had anything to do with it. I was unforunate enough to wipe my phone before I went to install the ROM, and it wiped the ROM too. When it restarted, it had nothing to boot too. Just used Fastboot to flash the aboot file, and sideloaded the ROM and flashed away
Click to expand...
Click to collapse
Had the same issue and same fix for my attempt into unlocking bootloader and installing custom recovery and rom.
Did you also flash the 5.8.0.19 aboot file? I'm wondering if flashing a newer one is a good idea...
Sent from my LEX727 using Tapatalk
Very good tool thank you very much Mauro
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Wortelstok said:
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Click to expand...
Click to collapse
The twrp 3.1.0 is better no matter the dev
Wortelstok said:
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Click to expand...
Click to collapse
Maybe yes, in the next Tool update i will update all recovery available, for now you can flash it through Manual Mode
mauronofrio said:
Maybe yes, in the next Tool update i will update all recovery available, for now you can flash it through Manual Mode
Click to expand...
Click to collapse
Thank you for all your effort for our Le Pro 3 :good:
Does this unlock bootloader with the current us version 21s?
I try using this Tool ALL in One on the Le Pro 3 but unable to unlock the bootloader as it displayed
"FAILED <remote: oem unlock is not allowed).
I already checked "ON under the OEM UNLOCKING" and "USB debugging" is "ON" also under the Developer Option before turning off the phone and boot it (volume down + Power) into Fastboot Mode.
Please help. Any advise is appreciated.
coolmaster121 said:
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
fastboot should be vol down
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
{
"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"
}
Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
Click to expand...
Click to collapse
How does your phone show up under device manager?
marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
View attachment 4281534
Click to expand...
Click to collapse
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.
Puddi_Puddin said:
How does your phone show up under device manager?
Click to expand...
Click to collapse
Device Manager lists the device as ONEPLUS A3003
DJBhardwaj said:
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.
Click to expand...
Click to collapse
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work
demonoid phenomenom said:
Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
I am on stock OOS with Marshmallow 6.0.1 and I am trying to update it to OOS 4.1.7 released on august 21st and I got the device just two days ago. I tried updating via OTA and it presented me with signature verification error and while trying to sideload the OTA, I ended up with the error mentioned above.
marmeak7 said:
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work
Click to expand...
Click to collapse
Have you tried flashing the full ROM zip file via stock recovery?
DJBhardwaj said:
Have you tried flashing the full ROM zip file via stock recovery?
Click to expand...
Click to collapse
The stock recovery does not have the option to flash zip files or am I not seeing the option?
marmeak7 said:
The stock recovery does not have the option to flash zip files or am I not seeing the option?
Click to expand...
Click to collapse
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.
DJBhardwaj said:
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.
Click to expand...
Click to collapse
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus
marmeak7 said:
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus
Click to expand...
Click to collapse
Oh.. How about installing TWRP and then flashing the ROM through that?
DJBhardwaj said:
Oh.. How about installing TWRP and then flashing the ROM through that?
Click to expand...
Click to collapse
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help ?
marmeak7 said:
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help
Click to expand...
Click to collapse
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.
DJBhardwaj said:
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.
Click to expand...
Click to collapse
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
demonoid phenomenom said:
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
Exactly, all courtesy of OnePlus. Not all OEM offer this liberty.
Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!
info2shail2010 said:
Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!
Click to expand...
Click to collapse
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:
marmeak7 said:
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:
Click to expand...
Click to collapse
Just in case you run into a brick...?..I did once so I found this thread handy
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
So i encountered this problem a while back, after doing some digging and analyzing adb, i came to the conclusion that adb could only address memory in 32bit on pc, so it couldn't handle the size when sideloading the extracted OS with STOCK recovery. If you want to still do it with stock you will have to do some digging around in forums, i found a software that modded the program to be able to use 64bit memory access. cant give you the link though since it was a while back.
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, NFC did not work for me even on stock bl locked firmware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
just flash a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
metalspider said:
just faslh a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
Click to expand...
Click to collapse
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
{
"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"
}
Free phones welcomed.
pl1992aw said:
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
Free phones welcomed.
Click to expand...
Click to collapse
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Ghostface009 said:
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Click to expand...
Click to collapse
As you wrote earlier, you had root access before MIUI update.
Once you get root, use Debloater to debloat the updater.
Code:
com.android.updater
is one of it.
Maybe there's other ones, but I don't have this phone, can't tell much about it.
Ghostface009 said:
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
Click to expand...
Click to collapse
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Issue solved after flashing unmodified boot.img, thanks all.
laid1995 said:
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Click to expand...
Click to collapse
Unfortunately it doesn't boot, I entered the fastboot command and it's just a black screen. I guess this doesn't work with MIUI 12.5.1, and that means Im stuck without root thanks to xiaomi
I also tried the adb command to remove magisk modules, didn't work, says inaccessable or not found
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Alin45 said:
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Click to expand...
Click to collapse
...But they did tho
The phone boots now, but still, I lost magisk and now I cannot install it on this update.
The phone also can't pass safetynet for some reason, despite having stock boot.img restored and leaving no trace of magisk.
All that could've been avoided if the device just did as it was told to, not to automatically update itself.
reg66 said:
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Click to expand...
Click to collapse
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Ghostface009 said:
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Click to expand...
Click to collapse
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Alin45 said:
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Click to expand...
Click to collapse
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Ghostface009 said:
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Click to expand...
Click to collapse
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Alin45 said:
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Click to expand...
Click to collapse
Maybe due to the difference between global and eu roms
Ik you gave all you can but what would you suggest to do for my situation in order to root this phone and pass safetynet again?
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Download the TWRP again.
Follow the guide with pictures: https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs steps up to step 13. Ignore step 8, 9 and the flash part of 12.
If this way still can't get you TWRP, then you might want to try latest MIUI by Xiaomi.eu. Read somewhere it has built in TWRP, so once flashed, you have TWRP. Verify yourself by reading in other posts though.
Remember
EEA (official) is different from Xiaomi.eu (custom ROM)
Click to expand...
Click to collapse
reg66 said:
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Click to expand...
Click to collapse
yep, the one I used was '2' version. I double checked for corruption and downloaded the same twrp again with same result :/
pl1992aw said:
Do Clean Flash custom ROMs
Click to expand...
Click to collapse
So my only way to get magisk again is flashing custom roms? it is how it is? :/
I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
EDIT
I bought USB OTG adapter and can flash from usb stick, only problem is that i can't transfer files from PC to phone while in twrp.
Debeciak said:
I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
Click to expand...
Click to collapse
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
pl1992aw said:
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
Click to expand...
Click to collapse
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
TWRP is in alpha
Debeciak said:
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
Click to expand...
Click to collapse
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
{
"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"
}
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
pl1992aw said:
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
Click to expand...
Click to collapse
As I said I tried to wipe everything (including format data), pretty much everything that is on forum i tried it.
Robert314 said:
TWRP is in alpha
Click to expand...
Click to collapse
So it is twrp fault? And if it is will it maybe work in future?
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
Post screenshots what error it's showing to you, so people know what it means.
pl1992aw said:
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
View attachment 5345137
Post screenshots what error it's showing to you, so people know what it means.
Click to expand...
Click to collapse
Phone is stuck on POCO screen right now. I used offical eea rom.
Debeciak said:
Phone is stuck on POCO screen right now. I used offical eea rom.
Click to expand...
Click to collapse
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
pl1992aw said:
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
Click to expand...
Click to collapse
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Debeciak said:
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Click to expand...
Click to collapse
Wait for it.
It takes some time for first booting. (wait 10 minutes)
pl1992aw said:
Wait for it.
It takes some time for first booting.
Click to expand...
Click to collapse
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Debeciak said:
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Click to expand...
Click to collapse
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Debeciak said:
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Click to expand...
Click to collapse
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Then use the built-in updater to update. Hope this work.
pl1992aw said:
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Click to expand...
Click to collapse
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Debeciak said:
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Click to expand...
Click to collapse
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
pl1992aw said:
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
Click to expand...
Click to collapse
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
I went through something like this as well.
As long as you can boot into fastboot. Then no worries. Just Flash the official stockrom. If something goes wrong. Reboot into fastboot (everytime you do something through fastboot. If you keep doing multiple processes, you'll keep having errors, always. Well that's what I went through. Rebooting into fastboot fixed my problem)
But your last pic declares that it was successfully flashed though.
Debeciak said:
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
Click to expand...
Click to collapse
When u flash xiaomi.eu, u set up the pin/pattern code in order to decrypt the internal storage in twrp?
Idk what's happening there.
It's just, flash xiaomi.eu via fastboot, boot it and set up pin/pattern code, fastboot boot twrp.img, go to twrp, insert the pin or pattern to decrypt internal storage and flash the latest update from xiaomi eu, simple as that..
And I don't get what's the A or B slot thing, I didn't had to chose or touch any of that, I saw that thing in twrp but didn't touched it..