Hi all.
Have bricked my Mi 10 Ultra China Rom.
Have tried to flash a multi Xiaomi.eu Rom. Tried
TWRP. Tried to flash back to Stock Rom with XiaoMiTool V2.
Now, have Stock Recovery. Device hangs by the first white MI Logo in a Loop.
I can boot into Fastboot but adb devices don't shows
the Phone.
Well, any, any Help will be appreciated.
Helmut
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Thanks for the fast Reply, ToneLa
Sorry for the Delay, had to charge the Phone!
Have done it like you described: Downloaded the special fastboot.exe, copied it in the "platform-tools-windows"-Folder of the ROM "xiaomi.eu_multi_MI10Ultra_20.9.3_v12-10-fastboot"
and start the Flash Process with the Batch File"windows_fastboot_first_install_with_data_format.bat". Right after the Phone restarts i pressed the Volume-Up Button and cleared the Caches
with "Wipe Data". Was a little of a Blind Flight because all was in Chinese!
After a couple of Minutes the Phone starts in my Language (German)!
Thanks a Lot for the Hint with the special fastboot.exe, i have tried this with the fastboot.exe from the ROM and from the ADB Developer Suite but with no Luck. Ended always in a Loop Boot.
Helmut
Sehr gut
Very happy this worked for you. The key is always fastboot.. The latest release is bugged, its not the ROM's fault, it's very annoying & will cause people grief!
But this is good news, it wasn't bricked, this is why I help people... It feels good when you help a bad situation
Enioy your phone, it will be like new!
helmut.eder said:
Hi all.
Have bricked my Mi 10 Ultra China Rom.
Have tried to flash a multi Xiaomi.eu Rom. Tried
TWRP. Tried to flash back to Stock Rom with XiaoMiTool V2.
Now, have Stock Recovery. Device hangs by the first white MI Logo in a Loop.
I can boot into Fastboot but adb devices don't shows
the Phone.
Well, any, any Help will be appreciated.
Helmut
Click to expand...
Click to collapse
Format data after flash eu rom
dungnghien said:
Format data after flash eu rom
Click to expand...
Click to collapse
Thanks for the Hint! ??
Perhaps...the Updater App on my Phone shows an Update to 20.9.17!
Can't see if this is a Multi Language Rom or China.
Does the Updater now shows only Equal Rom like the installed?
Thanks in advance
Helmut
helmut.eder said:
Perhaps...the Updater App on my Phone shows an Update to 20.9.17!
Can't see if this is a Multi Language Rom or China.
Does the Updater now shows only Equal Rom like the installed?
Thanks in advance
Helmut
Click to expand...
Click to collapse
Updater App doesn't work without TWRP or flash manually. You can reboot to recovery and if you have TWRP you can install it that way (but wipe too within TWRP)
I'm on that one. Weekly and stable are different... Both are multi language, that's the point of the EU Rom
Few bugs in each. I don't think you'll lose anything moving.
But you'll need to do it in TWRP so get that sorted! Flash it like you've done before... And if you switch between them, wipe to prevent errors
I like the weekly rom, some bugs. Videos are green if you use stabilisation. Settings search crashes if you are too slow!
But brilliant.
I would say install weekly if you want to be on the cutting edge and are prepared for some small bugs.
Stable is for 99% of users
And really this is where you want to be. Any new rom will need TWRP then root. I also rooted my phone with latest magisk
Root is great but some banking apps don't work. It's a personal choice, don't rush into it
Thanks for the Insight, ToneLa.
Will stay at the Moment with the 20.9.3.:angel:
Maybe later i will try an Update with the fastboot.exe
and Update Batch File from the Rom.
Thanks for your Efforts.
Helmut
helmut.eder said:
Thanks for the Insight, ToneLa.
Will stay at the Moment with the 20.9.3.:angel:
Maybe later i will try an Update with the fastboot.exe
and Update Batch File from the Rom.
Thanks for your Efforts.
Helmut
Click to expand...
Click to collapse
That rom is great. Weekly is hardly different...!
I did not use the batch files for updating. If you want to update, put on Chinese TWRP, download the update via updater and when at 100% do Reboot to Recovery option (it won't install).
Install in TWRP then wipe and reboot (I didn't even need to wipe... But it's good to)
Going forward the usual way with the EU ROM is via TWRP so it's good to have it
TWRP isn't official yet, suppose you know we are using an odd Chinese version we set to English.. Can dig out the link if you have no idea what I'm talking about
Hi all, I have the same problem: I have a MI Ultra, unlocked the bootloader (waiting for a week), and now I am stuck in a bootloop. I tried what you wrote:
Downloaded the ROM, replaced the fastboot.exe, used the batch file (seem to work without errors), Volume up on first restart, wipe, but I am back in a loop restarting every 2 minutes.
No problem to get into TWRP or Fastboot.
What shall I do?
EDIT::::: No idea why, tried the same thing again, now it works....
Always best to format, not just wipe on first boot. The bat file should do it when using a fastboot ROM, it may not have fully done that, hence the bootloop. But when you use your first .zip file flash from twrp, format data, not just wipe and again if you change ROM branches between stable and weekly.
Sathelp said:
Always best to format, not just wipe on first boot. The bat file should do it when using a fastboot ROM, it may not have fully done that, hence the bootloop. But when you use your first .zip file flash from twrp, format data, not just wipe and again if you change ROM branches between stable and weekly.
Click to expand...
Click to collapse
Big thank you all that contributed to that thread, I have now a great phone with German ROM.
Would you recommend me to use stable or weekly? I have weekly now and everything seems to work fine...
OnkelAlbert said:
Big thank you all that contributed to that thread, I have now a great phone with German ROM.
Would you recommend me to use stable or weekly? I have weekly now and everything seems to work fine...
Click to expand...
Click to collapse
Weekly gets the latest features, but there's a slight risk that a new weekly release might contain bugs that went unnoticed during internal testing by the devs.
The way I do it, is that I'll run weekly - and everytime a new weekly version gets released, I'll wait about 4 days before updating to it.
That's usually enough time for any critical bugs to surface.
Please remember that if you change branches between stable and weekly, you must format data as there may have been a change of partition tables and you could end up with bootloop again.
ToneLa said:
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Click to expand...
Click to collapse
hello, i have problems with my 10 ultra. Person I'm new to this, I have downloaded the zip and the fasboot exe but now I don't know how to do it. There is a youtube type tutorial or manual to do steps. thanks i am somewhat lost. i need help
Here is my guide.... https://mega.nz/file/6UAhXCxZ#Np2KwhMnl8obmOvp4b-2R9ajo0zrtz3vwefy-Ya3PLs
Let us all know how you get on. We're here to help you, so no question is a silly question
ToneLa said:
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Click to expand...
Click to collapse
Hi, I'm totally stuck... my phone just reboots in TWRP every time no matter what I try.
I just went through the instructions above as a final hope.... but no... completed and rebooted in TWRP...
Can anyone advise how to get out of this?
Thanks in advance.
Update after trying everything I could find on the web and just short Frisbeeing the phone out of the window I reinstalled the Chinese factory recovery, cleared the data .... rebooted and it worked!
Did you format after installing the ROM in twrp? Not just wipe but a proper format where you have to type yes to continue?
Please don't panic, your phone will be fine. Just install the ROM, format and reboot system. Here is a link to my guide.
File on MEGA
mega.nz
Hi guys, I just got my mi 10 ultra today, and now I want to change the rom to eu since I live in Europe... but I am afraid because I see that there are some camera changes in this custom room..? can anyone test out official and custom and confirm it there are such differences because I bought the phone just for it's cam
Related
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?
Hey everyone, I'm in a pickle with mi Ultra.
I'll walk you through the key events that led me to where I am now.
Yesterday, I noticed my battery was being used up fairly quickly, the battery settings showed that "other" had drained my battery 16% over the course of a few hours. I decided I wanted more info so I got recommended to try installing Gsam and it's root addon to see if I could get more details.
At this point in time, I was on EU rom with Magisk running smoothly, after installing Gsam and the root addon it wanted me to reboot, and so I did. That was the last time since then that I have been able to get in to my phone.
It started with a bootloop, so I tried unrooting via TWRP, wiping cache, nothing.
After a while i said **** it, if I lose my data so be it. Tried dirty flashing the EU rom again, no luck. And now I couldn't see /data no more in TWRP.
Decided to try a fresh install of EU rom, formatted data via TWRP and installed EU rom again, still no.
So then I tried following the guide I followed orginally to install the EU rom via my PC, nope again.
Maybe the china rom could help here? Tried installing it via fastboot command-line - nope, via sideload - nope, via MiFlash - no.
The loop has during these hours of terror behaved differently, but the farthest I've gotten is being able to type in my wifi Password to start trying to unlock my Mi account, but just after that, the touch becomes unresponsive and "System has stopped responding" and then reboot.
So, I turn to you guys for help, I've followed all guides/forum threads that I could find about bootloops and bricking on the ultra (including the ones here of course) but so far none of those tips have solved my problem.
Does anyone have any more things that I could try?
If need be I can post a video of the problem as it occurs.
Thanks in Advance, Chris
After any branch change flash, did you format? If not, it will boot loop. No good formatting before flashing, it must be done after. I would start again by going to fastboot and install the original stock Chinese ROM. This will replace twrp with stock recovery. Get a fastboot ROM from mifirm.net .
Once done, then check it's working Ok and build on that with flashing twrp from fastboot and then a twrp ROM. BUT after flashing any same branch ROM, you must wipe cache and dalvik. If you change branch like stock to EU or stable to weekly, you must format data as there may be different partition differences. It is very hard to brick an Xiaomi phone as you will always have access to fastboot. Just one word of advice, if you choose the first EU fastboot ROM, you need to swap out the fastboot.exe as it had an issue but other than that slow down take your time and it will work. Good luck.
I flashed a custom rom on this phone a couple of months back and after a week of use I handed it down to my sister-in-law. Accordingly she updated it and it got stuck in a BOOTLOOP (fastboot screen) since yesterday.
I've already posted this yesterday on the Phone's thread.
Please do help me. Thank you!
senyoreeto said:
I flashed a custom rom on this phone a couple of months back and after a week of use I handed it down to my sister-in-law. Accordingly she updated it and it got stuck in a BOOTLOOP (fastboot screen) since yesterday.
I've already posted this yesterday on the Phone's thread.
Please do help me. Thank you!
Click to expand...
Click to collapse
You didn't need to change the system file, this won't help to this issue.
It's uncertain to know if the Miui ROM that you tried to install was older or newer that the firmware you had previously, a downgrade is not allowed.
When you are coming from a custom ROM and tried to return to Miui (as you tried to install a Miui ROM) you have to do it through fastboot or through EDL mode, I say that so is not clear why exactly you tried to do that.
Finally, if the firmware where you are now is the right to flash the custom ROM you want, by flashing that custom ROM directly would be enough (of course after following the given steps on that thread) no need to flash the whole stock ROM prior to do that (at least is explicitly indicated)
Before to do anything, go back to the original format file.
@SubwayChamp there's a problem with the partitions being encrypted even though I do:
WIPE > FORMAT DATA > YES
the error shown in the picture comes up. same as trying to flash anything
senyoreeto said:
@SubwayChamp there's a problem with the partitions being encrypted even though I do:
WIPE > FORMAT DATA > YES
the error shown in the picture comes up. same as trying to flash anything
Click to expand...
Click to collapse
The partition being encrypted is not really an issue, some devices keep encrypted no matter which ROM you flash or if even you format data.
The feature repair file has to be used wisely, you have to go back to the original system format file.
The better you can try now is flash the stock ROM not through recovery but through fastboot (firstly) and after that, if fastboot doesn't fix it, through EDL (download mode) take care to not lock it again.
From there, you should start again from the scratch.
@SubwayChamp - firstly thank you for the help. Ill update you soon.
@SubwayChamp
I tried flashing the stock firmware using MiFlash Tool, but nothing happens it just says success yet the phone stays at the fastboot screen.
Then I tried EDL mode, even cracked the plastic back cover :'(
The port registered and used the flashtool again but still, the software just closes whenever I flash.
So I did a bit more research and found this. Had to flash everything line by line and now the phone has come back to life. Thank you!
Hi, i just got my old 5 year old (now retired) device to bootup because someone had made a kernel for the device which supports overclocking so for the fun I wanted to try it
but there was one weird problem, it seemed that though the root permissions from years ago remained just like they were but magisk manager itself had lost root permissions though I was still able to grant root permissions to other applications normally
I was on an unofficial Lineage OS build and thought of returning to original Miui for the device, got the fastboot rom, got Mi flash, flashed it, booted up
but there was a catch, it would always throw an error on the login Miui account screen at startup saying "Couldn't check device security, please try again"
I had tried everything possible including:
adding a Xiaomi account
skipping sign in
Inserting a sim
None of them seemed to do anything so i flashed twrp recovery again as using mi flash to flash ur device's stock rom gets rid of custom recovery
Now here is the mistake I made
**I wiped the device clean using TWRP**
now i tried going into adb sideload mode, no matter what I did my PC wouldn't detect my device, tried going into fastboot mode and still my PC wouldn't recognise the device and same goes for Mi flash tool
additionally the device would automatically exit out of fastboot mode within 2 minutes and go on to the power off screen
I do have charge on the device it says it's at 87% on the TWRP menu
I can no longer bootup, im stuck at the MI logo on bootup
Device: Mi Max 2
Additional notes: I am not in a hurry as that is not my primary device so it is okay if you want to take your time to reply, even if there's no way i can get my phone to see the light of day again it's alright as the phone was retired and sitting collecting dust for 2 years now
I do not wish to visit a service center as it's not worth it for a device I'm just gonna use for a few hours then put it back into its grave again
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
kraken-gz said:
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
Click to expand...
Click to collapse
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
BR4UTAL said:
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
Click to expand...
Click to collapse
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
kraken-gz said:
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
Click to expand...
Click to collapse
Tried wiping data, cache and dalvik cache and formatting data, none seemed to help
and still no sd card being detected
Now edl mode
I would love to boot into edl mode but the thing is my device isn't being recognised by adb nor is it being recognised by fastboot commands
so that's where I'm stuck for now
OldNoobOne said:
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
Click to expand...
Click to collapse
Perhaps that is true