Database Develop

[Q] Nexus 7 Nakasi factory .img wont flash

Hi guys im new to the nexus 7, i have previously owned a samsung galaxy s wifi 4.0(piece of crap), i had unlocked and rooted my nexus using the nexus root toolkit v1.6.3. Then i flashed francos latest release kernel through the francos kernel app, Next i downloaded the beats+xlouder mod, i attempted to flash it through cwm by installing zip, it seemed to work, booted then said, something about configuring apps and it got stuck on that. I tried rebooting many times but it didnt work. So then i tried to flash a nandroid backup i had made through the toolkit, this failed. Now i have been trying to flash the nakasi factory image through the toolkit, here is the message i get;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any ideas as to whats going on? and how i might get the nexus working again?

Don't use toolkits.
Apparently, your bootloader won't flash correctly. What version is your bootloader now? If you want to flash android 4.2.2, then it should be 4.18.
Check your USB-cable. If possible, use the one that came with the nexus 7. Check your bootloader img-file. Is the md5-sum correct? If uncertain, then redownload the firmware here: https://developers.google.com/android/nexus/images#nakasi
Extract the contents of the firmware file in your folder with adb and fastboot.
Put your nexus 7 in fastboot/bootloader mode (you can do this by pushing all three buttons on the sides simultaniously).
Type (this will erase everything from your device):
: fastboot erase boot
: fastboot erase cache
: fastboot erase recovery
: fastboot erase system
: fastboot erase userdata
If you need to update your bootloader, then type:
: fastboot flash bootloader bootloader-grouper-4.18.img
If you get an error like signature failed, then recheck your USB cable. This should work. If not, then download the android 4.1.2 firmware and skip flashing the bootloader. You can do an OTA update later.
: fastboot reboot-bootloader
Then type:
: fastboot -w update image-nakasi-jdq39.zip

I had a few troubles on my first attempts too... My suggestion is to get Nexus7 Toolbox from the Sticky in the Development section and flash the image you have, that always worked without a hitch for me!
Good luck!

Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium

random hero said:
Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium
Click to expand...
Click to collapse
Probably not, but I have seen forum posts where people reported different experience with different cables used to flash firmware. I only experience it when charging. My nexus charges faster with the original cable and charger. Also the original cable's small end is slightly longer than the small end on the cable I got with my samsung smartphone. If it makes any difference when flashing? I am not sure, but to rule out bad USB-cables as a reason for firmware not flashing I always use the original cable.

My bootloader versin is 4.18, how exactly do i check md5 sums,?
i have no experience with fast boot and adb, are they pc programs? If so cqn you give me a link to them?
Sorry im sure you guys get sick of idiots like me asking questions all day but i really appreciate the help

If your bootloader version is 4.18, then there is no need to reflash it and you can skip this step. Don't worry about feeling idiotic for asking questions. Up until I first rooted my nexus, I had no idea how everything worked either. I learned everything by myself, but it's not that easy for everyone.
You can find adb and fastboot in the folder platform tools in the official google android SDK. Instead of downloading the entire SDK, you can also just download the latest platform tools online from many file share websites: https://mega.co.nz/#!1c1XjIIC!dTyG200R4V3BPIfrac4xayEttP02f9tYlPkqAlqvTko .
Extract that folder. Go to that folder. Hold shift and click with your right mouse button and select open terminal prompt.
Now you can use fastboot to flash images, recoveries, bootloaders, erase your devices, restore, etc.....

yeah ok, ill try it and fingers crossed that it works

i tried to flash it but it says
error: failed to load 'image-nakasi-jdq39.zip
the file i have is a .tar, would that be the problem?

Yes! We found the problem.
You need to unzip the tar file as well. 7-zip can do this for example.

thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:

TheFro74 said:
thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:
Click to expand...
Click to collapse
http://www.modaco.com/forum/657-google-asus-nexus-7-nexus7modacocom ... but I would say that wouldn't I, given it's my own ROM of choice.
Leaving aside my own personal preferences, check out these two threads for ideas and recommendations...
http://forum.xda-developers.com/showthread.php?t=2151963
http://forum.xda-developers.com/showthread.php?t=1807811
The question you have to ask yourself is... do you want full-on functionality, with shed-loads of bells and whistles... or a lean, mean, and minimalistic ROM... or, perhaps something inbetween.
The choice, as they say, is yours....
Rgrds,
Ged.

One of the fun things about the nexus 7 is to experience different roms yourself. See what they differ, what they have in common, what you like about them, etc. I liked paranoid android a lot. I found it very creative, but it didn't ran fluent for me. I even tried ubuntu, but that's just not ready for daily use yet. Now I settled for CM 10.1 M3. It's very stable, smooth and provides a better experience than stock, which I was looking for. But it might be too basic for you. Try it out! And make NANDROID BACKUPS before you do!

Thanks guys , my current setup is a cm10.1 snapshot with Franco's kernel.
Sent from my Nexus 7 using xda app-developers app

[RECOVERY][OFFICIAL] TWRP 3.2.1-0 touch recovery

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
/*
* [B]Your warranty is now void.[/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Sources: https://github.com/TeamWin
Device tree: https://github.com/TeamWin/android_device_huawei_charlotte
Download
Flashing:
Code:
fastboot flash recovery_ramdisk twrp-3.2.1-0-charlotte.img
Special thanks to @Dees_Troy for the Huawei Blanc device tree, which this is based on.

Thank you so much Is there any chance of you uploading a twrp flashable image of the newest p20 pro update?

Will try this when I get home. It doesn't replace eRecovery, right? So I can still recover if anything goes wrong? Also, best way to boot into TWRP once flashed?

danifilth4king said:
Will try this when I get home. It doesn't replace eRecovery, right? So I can still recover if anything goes wrong? Also, best way to boot into TWRP once flashed?
Click to expand...
Click to collapse
As long as you flash the image to recovery_ramdisk it does not replace eRecovery, no. I actually used eRecovery to restore while testing my build.
Once flashed you can boot into TWRP via "adb reboot recovery" out of a running system with enabled ADB or via pressing VolUp+Power on a powered off device.

Many thanks a1Pha, just installed on a CLT-L29 8.1.0.106(C432), works flawless. Great job !
Once flashed you can boot into TWRP via "adb reboot recovery" out of a running system with enabled ADB or via pressing VolUp+Power on a powered off device.[/QUOTE]
You can also reboot to recovery if your phone is up and running opening Magisk Manager -> Modules, three points on the upper right corner will give you the choice recovery, bootloader or download...
Cheers.

buenso80 said:
Thank you so much Is there any chance of you uploading a twrp flashable image of the newest p20 pro update?
Click to expand...
Click to collapse
To be honest: This is my first Huawei and I am still figuring out how they manage their region-specific customization. Also it seems not so easy to get the UPDATE.APP for current builds. So no promises here - but I'll try to figure out and create a new thread if I'm able to build something.

Thanks given! I'll try this when I get a chance! This is a good start for this new device

a1Pha said:
To be honest: This is my first Huawei and I am still figuring out how they manage their region-specific customization. Also it seems not so easy to get the UPDATE.APP for current builds. So no promises here - but I'll try to figure out and create a new thread if I'm able to build something.
Click to expand...
Click to collapse
Maybe this could be usefull?
https://forum.xda-developers.com/hu...rmware-release-clt-l29-8-1-0-107c432-t3779167

buenso80 said:
Maybe this could be usefull?
https://forum.xda-developers.com/hu...rmware-release-clt-l29-8-1-0-107c432-t3779167
Click to expand...
Click to collapse
Thanks. As soon as I've got a fully working system.img which doesn't break different country models you'll hear from me.

Does it work for the CLT-L09 as well?

llvllorpheus said:
Does it work for the CLT-L09 as well?
Click to expand...
Click to collapse
Yes, I'm actually on CLT-L09!

llvllorpheus said:
Does it work for the CLT-L09 as well?
Click to expand...
Click to collapse
Works perfect

a1Pha said:
As long as you flash the image to recovery_ramdisk it does not replace eRecovery, no. I actually used eRecovery to restore while testing my build.
Once flashed you can boot into TWRP via "adb reboot recovery" out of a running system with enabled ADB or via pressing VolUp+Power on a powered off device.
Click to expand...
Click to collapse
How do you get back into eRecovery once you have flashed twrp?
Volume up gets you to twrp - is there a special key combo/sequence to get to eRecovery? I as as I have access to funkyhuawei. Also - how would one go back to stock with this installed? Sorry first time doing this for years
Cheers
Andy
---------- Post added at 06:52 PM ---------- Previous post was at 06:30 PM ----------
Ok so I managed to get into eRecovery by powering off and holding vol up and pwr until the phone vibrated, then release power and continued holding vol up until eRecovery appeared. If I wanted to completely remove TWRP and root etc once in eRecovery would it simply be a case of clicking download latest version and recovery? Then once recovered I could relock the bootloader? Or are there some other steps to do?
If anyone could help so I know for future reference that would be amazing. Thank you in advance

andrewglass3 said:
How do you get back into eRecovery once you have flashed twrp?
Another way to enter eRecovery: Shut down phone, press VOL+ and connect to USB... and wait
Click to expand...
Click to collapse

andrewglass3 said:
If I wanted to completely remove TWRP and root etc once in eRecovery would it simply be a case of clicking download latest version and recovery? Then once recovered I could relock the bootloader? Or are there some other steps to do?
If anyone could help so I know for future reference that would be amazing. Thank you in advance
Click to expand...
Click to collapse
Glad you made it
I used eRecovery after I bricked my recovery partition and ended up with a working stock recovery, so yes, that should be the way. I did not try to relock the bootloader though.

Official builds from twrp.me are now available, OP updated.

a1Pha said:
Official builds from twrp.me are now available, OP updated.
Click to expand...
Click to collapse
i see pretorians TWRP has MTP working fine
but the official TWRP has not
if we decide to flash pretorians twrp and then yours, is that fine? or do we have to flash stock in-between?

virtyx said:
i see pretorians TWRP has MTP working fine
but the official TWRP has not
if we decide to flash pretorians twrp and then yours, is that fine? or do we have to flash stock in-between?
Click to expand...
Click to collapse
You should be fine switching between the builds as long as you don't touch other partitions.

a1Pha said:
You should be fine switching between the builds as long as you don't touch other partitions.
Click to expand...
Click to collapse
ty!
hopefully official can get MTP working fine fingers crossed.

Good day.
Can this use for rebrand from OCT652 to C636?
Thanks.

Device stuck in TWRP

Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
hey does your device have an working os ?

mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported

Benjamin0702 said:
hey does your device have an working os ?
Click to expand...
Click to collapse
Benjamin0702 said:
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported
Click to expand...
Click to collapse
Like I said, I am stuck in TWRP. I can't boot anything and I guess I don't have any os anymore.

Are you frozen in a black screen?

Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.

mrtr33 said:
Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.
Click to expand...
Click to collapse
You need to erase the "misc" partition.

VD171 said:
You need to erase the "misc" partition.
Click to expand...
Click to collapse
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext

mrtr33 said:
View attachment 5264227
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext
Click to expand...
Click to collapse
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/

VD171 said:
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Click to expand...
Click to collapse
Now I get the following error when trying to install the xiaomi.eu ROM form SD Card:
Code:
E: unable to update logical partition: /system_ext
E: unable to decrypt FBE device
After installating and rebooting I am back at TWRP again.

Trying to boot my Huawei P9 inot TWRP, stock rom always overwrites even if I boot into recovery correctly

As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23

Catnip202X said:
As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screenView attachment 5281583
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23
Click to expand...
Click to collapse
TWRP must be flashed with the command:
fastboot flash recovery_ramdisk ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help

zgfg said:
TWRP must be flashed with the command:
fastboot flash recovery ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help
Click to expand...
Click to collapse
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.

Catnip202X said:
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.
Click to expand...
Click to collapse
Yes, sorry, you are right, typo.
But I wanted to point that you must use fastboot flash command (not FLASHBOOT or whatever you used in your post #1)
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
But also READ the P9 LOS thread - it clearly describes that LOS must bi flashed from fastboot, not from TWRP and it actually asks users not to use TWRP
See here and better ask there to get the answers directly from developer:
[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9
This thread is dedicated to provide Lineage-OS 16.0 builds with microG included for the HUAWEI P9 with current security patches. It is a treble build, therefore it could also work on other devices, but I haven't tested. And yes, the camera...
forum.xda-developers.com

zgfg said:
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
Click to expand...
Click to collapse
I have indeed tried this route, but as I have stated before, trying to boot into recovery mode right after flashing TWRP and pressing key combo still boots me into the error screen where it says that I need to update something. On the bottom of the screen will also show errors such as Function11 not found and error 2 no image etc. I’ll try to replicate it and send you a picture of the error screen when I get home from work tonight.

Question Reflashing stock ROM on bootlooping device

Hi.
Bought this phone 4 months ago and it went into a boot loop, where it would only show the battery empty icon. Yesterday, I tried turning it on again and noticed, that it's stuck at the Redmi - Powered by Android" screen. From this screen, I can enter fastboot. See this video:
VID_20230417_194410.mp4
drive.google.com
I've read that there are a couple of options for reflashing this device:
- aks someone with the authorized Xiaomi account to reflash stock rom using the MiFlash tool (no bootloader unlock needed)
- put the device somehow into ETL mode and reflash stock rom using the MiFlash tool (no bootloader unlock needed)
I've tried contacting someone, who for #1, but they aren't willing to help, for some reason (I'm wiling to pay). For #2, I'd have to open up the device, which I'd like to avoid doing.
Would anybody know of any other options for fixing this?
Thank you in advance!

okay, which version of MIUI are you running?
first get the fastboot rom of the version your phone supports , i recommend the global version fastboot rom , because it works and its stable and u get your updates
download this fastboot rom first
Temporary file download page
miuirom.org
and I will give you the MI flash tool working version at like 6 hours after, Ill post the remaining steps after you download this , btw, you will get a .tgz file , when u download the Rom, thats the one you need

RunoTheDog said:
Hi.
Bought this phone 4 months ago and it went into a boot loop, where it would only show the battery empty icon. Yesterday, I tried turning it on again and noticed, that it's stuck at the Redmi - Powered by Android" screen. From this screen, I can enter fastboot. See this video:
VID_20230417_194410.mp4
drive.google.com
I've read that there are a couple of options for reflashing this device:
- aks someone with the authorized Xiaomi account to reflash stock rom using the MiFlash tool (no bootloader unlock needed)
- put the device somehow into ETL mode and reflash stock rom using the MiFlash tool (no bootloader unlock needed)
I've tried contacting someone, who for #1, but they aren't willing to help, for some reason (I'm wiling to pay). For #2, I'd have to open up the device, which I'd like to avoid doing.
Would anybody know of any other options for fixing this?
Thank you in advance!
Click to expand...
Click to collapse
If you can boot into fastboot, then it is already enough.
Now, I suppose your bootloader is still locked
You need to download a MIUI ROM from "EEA", from any trusted website, and remember to download the "Fastboot" ROM to flash it (my favorite is mifirm.net, it downloads faster)
Install MiFlashPro - attached at the end of the thread
Open it up, and you will be greeted with this.
Click on the "Mi Flash" tab, as it is the only one we need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will be greeted with this window now:
After you have done downloading your ROM, extract it to any place.
If MiFlash does not recognise the directory you have extracted in, move it to C:\. Not any external drive, your main one
Now click on the "select" button box, go to your ROM directory, and simply select its folder
Boot your device into fastboot (PWR + VOL-), click on "refresh" button box and your device serial number should appear on the first line.
Now simply click "flash" and let it do its job for 10 to 15 minutes. It will reboot automatically.
If you dont succeed, please read this thread:
Thread '[GUIDE] UNBRICK YOUR HARD-BRICKED MTK' https://forum.xda-developers.com/t/guide-unbrick-your-hard-bricked-mtk.4564029/
You will require BROM and to bypass and to flash via SP Tool.
RunoTheDog said:
For #2, I'd have to open up the device, which I'd like to avoid doing.
Click to expand...
Click to collapse
You have either got confused, or being scammed
Newer MTK devices do not require the opening of the device. I suppose you have been probably confused with a Qualcomm Snapdragon based service, that does require the opening, so you can access EDL mode and flash your phone into life, or someone just put up the Redmi Note 10 5G and is a scam, also, on MTK, you do not need to pay for a authorized Mi account. On MTK, it is easily bypassable due to BROM

Thank you both.
I put ran MiFlashPro, pointed it towards the downloaded eea stock rom file and attempted to flash it, but got this error message:
So I presume this is due to locked bootloader? I'll try to follow the second link.

I actually managed to enter recovery mode and do a factory reset. Currently setting it up and plan on updating it.

RunoTheDog said:
I actually managed to enter recovery mode and do a factory reset. Currently setting it up and plan on updating it.
Click to expand...
Click to collapse
Good to hear you got sorted. I basically bricked my phone last week (only 3 weeks old ) after trying to switch from MIUI 13 Global to EEA. I managed to get it into BROM mode and used MTK Auth Bypass which allowed me to use Chimera Tools to flash the phone again as nothing else seems to work with a locked bootloader. Currently running MIUI 14 with root and magisk optimisations (blur/high end tweaks, MIUI monet etc) and loving it! Just need a way to bypass Play Integrity API for Google Wallet