Related
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?
Hello everyone,
First of all, rom and recovery are not from me... I just want to make a full guide to help you
So let's go !!!!!
1 step: unlock bootloader
https://en.miui.com/unlock/
BE CAREFUL unlocking your bootloader will erase all your data (internal storage) so don't forget to make a backup
2 step: flash twrp recovery
Download the recovery image from here
https://drive.google.com/file/d/1-1CSfT4lQwFZngu6RI9eowLA9CmEMEPw/view?usp=drivesdk
Be sure to have adb and fastboot tools on your computer ... If not take a look at here
https://forum.xda-developers.com/showthread.php?t=2317790
Past TWRP_umi.img on minimal adb and fastboot directory.
Open a cmd here.
Enable usb debugging on your device
Reboot your phone on bootloader (hold volume down + power), connect it to PC and tape:
fastboot devices
fastboot flash recovery TWRP_umi.img
Then tape fastboot reboot while holding volume up button on your devices to reboot in recovery
3 step:
At the first launch of Twrp You have to choose SWIPE TO ALLOW MODIFICATION
4 step:
THIS ONE OF THE MUST IMPORTANT STEP
In twrp menu you have to go in Wipe data on choose format data
Otherwise the ROM will not boot.
5 step:
Reboot into recovery from twrp.
6 step:
Connect your phone to your PC and paste the xiaomi.eu ROM of your choice (stable or Dev)
7 step:
Flash ROM from recovery
8 step:
REBOOT AND ENJOY :good::good::good:
Does Xiaomi EU Rom run either on encrypted and unencrypted storage?
I cant get this to work, ive been trying everything for hours. I am sure i am missing something stupid but if anyone has any new ideas please let me know. I unlocked my device today, flashed twrp via fastboot, rebooted to recovery, formatted data then went on to install xiaomi eu rom. Ever since trying this, i am constantly booting into recovery or hitting a boot loop. i have formatted data more times than i care to think of ha ha. ive tried flashing the latest fastboot rom via mi unlock tool to do a fresh start but keep getting ''flash crclist error". Ive also tried flashing miui stock via twrp and it also, doesn't boot. ive tried many combinations in between. My next option is to try the fastboot global rom (though i believe i have a chinese device), i am waiting for it to download. If anyone knows what i am doing wrong i will be eternally grateful if you can tell me what it is. I'm so frustrated, been flashing roms for years, never had anything take as long as this :crying:
carolef1984 said:
I cant get this to work, ive been trying everything for hours. I am sure i am missing something stupid but if anyone has any new ideas please let me know. I unlocked my device today, flashed twrp via fastboot, rebooted to recovery, formatted data then went on to install xiaomi eu rom. Ever since trying this, i am constantly booting into recovery or hitting a boot loop. i have formatted data more times than i care to think of ha ha. ive tried flashing the latest fastboot rom via mi unlock tool to do a fresh start but keep getting ''flash crclist error". Ive also tried flashing miui stock via twrp and it also, doesn't boot. ive tried many combinations in between. My next option is to try the fastboot global rom (though i believe i have a chinese device), i am waiting for it to download. If anyone knows what i am doing wrong i will be eternally grateful if you can tell me what it is. I'm so frustrated, been flashing roms for years, never had anything take as long as this :crying:
Click to expand...
Click to collapse
try rhis
format data (not wipe)
put rom.zip unto ur internal storage
wipe cache an dalvik cache
now flash the zip
now reboot to recovery
wipe cache an dalvik cache
an now go to reboot menu
an now power off
an now power it on
-fluffy- said:
try rhis
format data (not wipe)
put rom.zip unto ur internal storage
wipe cache an dalvik cache
now flash the zip
now reboot to recovery
wipe cache an dalvik cache
an now go to reboot menu
an now power off
an now power it on
Click to expand...
Click to collapse
Thank you for trying to help, unfortunately it just rebooting to my recovery still. I dont suppose anyone has any other ideas do they please I cant understand what on earth ive done wrong. Does anyone know why mi flash tool comes up with that error (flash crc list error)? qualcomm drivers are installed.
carolef1984 said:
Thank you for trying to help, unfortunately it just rebooting to my recovery still. I dont suppose anyone has any other ideas do they please I cant understand what on earth ive done wrong. Does anyone know why mi flash tool comes up with that error (flash crc list error)? qualcomm drivers are installed.
Click to expand...
Click to collapse
write what u do wen u try to flash the zip
an have u downloadet the correct zip file
Thanks everyone, i think it must have been something to do with the qualcomm drivers installed incorrectly. i have re-done that from scratch and managed to get mi flash tool working. Sorry to waste everyones time.
Greetings
I have followed the tutorials to perfection like 2-3 times and I still face the same issue
I always go back to TWRP after trying to boot into system.
I have tried 2 different recovery files
The experimental one asks for a password. and the other one works but keeps going back to recovery after flashing.
MIUI 11 rom
MIUI 12 rom
No matter what I do It keeps going back to recovery.
It's my only device so I truly need help.
I have tried re installing everything already.
At this point I just want to install stock rom and keep using it without flashing anything please help.
PHONE FINALLY REBOOTING INTO SYSTEM. I myself don't know what i did!!!
Bootloop (stuck on 5G logo) after flashing Xiaomi.eu ROM
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.
The problems started when I tried to install Xiaomi.eu Custom ROM : xiaomi.eu_multi_MI10_V11.0.25.0.QJBCNXM_v11-10
Downloaded the Xiaomi.eu ROM to PC, then copied to the Download folder of the Phone.
Started phone in upload mode or TWRP. > Wipe > Swipe to Factory Reset + Format Data.
When formatting data I erase all folders in the phone, including the Xiaomi.eu ROM copied in the Download folder.
Some tutorials suggest to copy the Xiaomi.eu ROM from PC to phone after formatting the data, just by connecting the phone in TWRP to the PC, by going to > Mount and enabling MTP.
Tried this method but when I send the Xiaomi.eu ROM file to the phone the progress bas doesn’t move.
So I restarted the phone, without installing the Custom ROM, went through all the screens of initial phone configuration. Lost Magisk and root (but I supposed that it’s not mandatory to install Custom ROM). Copied again the Xiaomi.eu ROM zip file to the Download folder. Rebooted to TWRP. This time I just did Factory Reset but without Format Data. Then > Install to install the Xiaomi.eu new ROM. Cleared Dalvik Cache then reboot.
PROBLEM : bootloop. Stuck with the 5G logo forever, waited more than 30 min, no change.
Still have access to recovery TWRP and to bootloader mode. I suppose this is a soft brick?
I did > Wipe, Swipe to Factory Reset + Format Data, restarted… no change.
Copied this time the Xiaomi.eu ROM to a clean formatted (FAT32) USB drive. As shown in some tutorials, you can us an external USB drive via USB OTG to install the Custom ROM via TWRP.
Factory Reset + Format Data, then I installed again the same Xiaomi.eu ROM from the external USB. Still stuck in bootloop.
Please I need help to fix the problem
I’m not an expert developer, but I’m not a complete noob either.
This is the first time I have troubles with a brand new Xiaomi Phone.
It’s the first time I get a very expensive phone, but had no choice (they are getting very expensive), because I always buy a Flagship Xiaomi to get all the community support possible.
And I had to change the ROM to Xiaomi.eu, because the Official Global ROM is full of bloatware I had a good experience with Xiaomi.eu ROMs with my old Xiaomi Mi 4 and Mi 5.
At this point I don’t mind going back to stock MIUI Global ROM.
I suppose that with access to boot loader I can flash the Official ROM from PC with MiFlash2020-3-14-0? If it’s the case can somebody show me detailed steps to do that?
For Mi 10 Official Global there is the Stable Full ROM (miui_UMIGlobal_V11.0.2.0.QJBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBMIXM_20200328.0000.00_10.0_global_09b168ff9e) (3.76 GB). Which One to flash from PC with MiFlash?
I can’t afford to hard brick the device
Thank you very much.
andromomo said:
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.
The problems started when I tried to install Xiaomi.eu Custom ROM : xiaomi.eu_multi_MI10_V11.0.25.0.QJBCNXM_v11-10
Downloaded the Xiaomi.eu ROM to PC, then copied to the Download folder of the Phone.
Started phone in upload mode or TWRP. > Wipe > Swipe to Factory Reset + Format Data.
When formatting data I erase all folders in the phone, including the Xiaomi.eu ROM copied in the Download folder.
Some tutorials suggest to copy the Xiaomi.eu ROM from PC to phone after formatting the data, just by connecting the phone in TWRP to the PC, by going to > Mount and enabling MTP.
Tried this method but when I send the Xiaomi.eu ROM file to the phone the progress bas doesn’t move.
So I restarted the phone, without installing the Custom ROM, went through all the screens of initial phone configuration. Lost Magisk and root (but I supposed that it’s not mandatory to install Custom ROM). Copied again the Xiaomi.eu ROM zip file to the Download folder. Rebooted to TWRP. This time I just did Factory Reset but without Format Data. Then > Install to install the Xiaomi.eu new ROM. Cleared Dalvik Cache then reboot.
PROBLEM : bootloop. Stuck with the 5G logo forever, waited more than 30 min, no change.
Still have access to recovery TWRP and to bootloader mode. I suppose this is a soft brick?
I did > Wipe, Swipe to Factory Reset + Format Data, restarted… no change.
Copied this time the Xiaomi.eu ROM to a clean formatted (FAT32) USB drive. As shown in some tutorials, you can us an external USB drive via USB OTG to install the Custom ROM via TWRP.
Factory Reset + Format Data, then I installed again the same Xiaomi.eu ROM from the external USB. Still stuck in bootloop.
Please I need help to fix the problem
I’m not an expert developer, but I’m not a complete noob either.
This is the first time I have troubles with a brand new Xiaomi Phone.
It’s the first time I get a very expensive phone, but had no choice (they are getting very expensive), because I always buy a Flagship Xiaomi to get all the community support possible.
And I had to change the ROM to Xiaomi.eu, because the Official Global ROM is full of bloatware I had a good experience with Xiaomi.eu ROMs with my old Xiaomi Mi 4 and Mi 5.
At this point I don’t mind going back to stock MIUI Global ROM.
I suppose that with access to boot loader I can flash the Official ROM from PC with MiFlash2020-3-14-0? If it’s the case can somebody show me detailed steps to do that?
For Mi 10 Official Global there is the Stable Full ROM (miui_UMIGlobal_V11.0.2.0.QJBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBMIXM_20200328.0000.00_10.0_global_09b168ff9e) (3.76 GB). Which One to flash from PC with MiFlash?
I can’t afford to hard brick the device
Thank you very much.
Click to expand...
Click to collapse
try this
format data
reboot recovery
connect phone to pc
put zip file ro phone
wipe cache an dalvik cache
install zip
wipe again
reboot recovery
wipe again
go to reboot
power off the phone
now wen its shut down power it on
an it shut boot
it will take a litle time
andromomo said:
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.JBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBM
Thank you very much.
Click to expand...
Click to collapse
hi didt it work for u
IT WORKED properly like a charm!!!
Dear -fluffy-,
Thank you very much for your quick reply.
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.
---------- Post added at 12:57 PM ---------- Previous post was at 12:47 PM ----------
Dear -fluffy-,
Thank you very much for your quick reply.
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.
---------- Post added at 01:15 PM ---------- Previous post was at 12:57 PM ----------
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.
Quick questions, do netflix and google pay work after the flash?
tott2003 said:
Quick questions, do netflix and google pay work after the flash?
Click to expand...
Click to collapse
yes
cedric3320 said:
4 step:
THIS ONE OF THE MUST IMPORTANT STEP
In twrp menu you have to go in Wipe data on choose format data
Click to expand...
Click to collapse
Hello,
i have a silly question about step 4:
someone says we should "Wipe Data", someone says we should "Format Data" ,
i don't see a real difference unless we want to change the filesystem type.
Advices ?
And also, when we format ( or wipe ) the "Data" partition, are we formatting the 256 GB partition ?
if yes, this is a really huge drawback for us who want to change ROM more frequently than other android users, because we have to backup a 256 GB partition ...
This is not fast to do online ( at least with my poor connection ) and it is not fast to do on PC or on a USB KEY.
So we have 256 GB and we need to format at each ROM change ? Too bad ...
In the good old times i did extract my microSD card and i was safe .
Someone could explain me please ?
thank you all for your patience...
adario73 said:
Hello,
i have a silly question about step 4:
someone says we should "Wipe Data", someone says we should "Format Data" ,
i don't see a real difference unless we want to change the filesystem type.
Advices ?
And also, when we format ( or wipe ) the "Data" partition, are we formatting the 256 GB partition ?
if yes, this is a really huge drawback for us who want to change ROM more frequently than other android users, because we have to backup a 256 GB partition ...
This is not fast to do online ( at least with my poor connection ) and it is not fast to do on PC or on a USB KEY.
So we have 256 GB and we need to format at each ROM change ? Too bad ...
In the good old times i did extract my microSD card and i was safe .
Someone could explain me please ?
thank you all for your patience...
Click to expand...
Click to collapse
Hello,
You have to format data the first time you flash xiaomi.eu rom because their rom is base on Chinese firmware (if you don't or just wipe it will not boot)
Each time you will flash a rom with different base (from Chinese base to global base or global to Chinese) you will have to format data !!
You format data to remove encryption.
tott2003 said:
Quick questions, do netflix and google pay work after the flash?
Click to expand...
Click to collapse
Google pay isn't working as the safety net doesn't pass on stable realeses, someone made it to work on betas but I had no luck though
Stuck without solutions
Hello,
I tried to flash the latest miui 12. I followed all the steps...
But now I can't acess recovery nor rom.
Basically when i try to flash TWRP with bootloader it just goes back to fastboot.
Also note that the flash is successful. But I somehow can't acess TWRP, just goes back to fastboot
And when I flash the experimental TWRP on the dev thread it boots to recovery but asks for a password.. Impossible to flash anything.. Even after I formated data and everything
I tried flashing other TWRP I found but nothing boots even after trying a lot of time.
I tried <fastboot boot recovery.img> as well
I tried <fastboot erase recovery> and then flash the TWRP as well
I've been trying hard for the last 8 hours.
I also have a backup of when I had MIUI 12. But impossible to flash it with the only recovery I can boot to.
I feel so desperate. I'm out of ideas.
If you have any ideas, I'm listening
Thanks for the help guys.
Dallee said:
Hello,
I tried to flash the latest miui 12. I followed all the steps...
But now I can't acess recovery nor rom.
Basically when i try to flash TWRP with bootloader it just goes back to fastboot.
Also note that the flash is successful. But I somehow can't acess TWRP, just goes back to fastboot
And when I flash the experimental TWRP on the dev thread it boots to recovery but asks for a password.. Impossible to flash anything.. Even after I formated data and everything
I tried flashing other TWRP I found but nothing boots even after trying a lot of time.
I tried <fastboot boot recovery.img> as well
I tried <fastboot erase recovery> and then flash the TWRP as well
I've been trying hard for the last 8 hours.
I also have a backup of when I had MIUI 12. But impossible to flash it with the only recovery I can boot to.
I feel so desperate. I'm out of ideas.
If you have any ideas, I'm listening
Thanks for the help guys.
Click to expand...
Click to collapse
an what is the latest miui12 u try to flash
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.
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
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