Related
Is there any possible way of accessing the internal storage through TWRP? I made the unfortunate mistake of wiping everything including the OS. I would like to access the internal storage drive so I can put in a ROM and flash. Any help would be greatly appreciated!
olive.knight said:
Is there any possible way of accessing the internal storage through TWRP? I made the unfortunate mistake of wiping everything including the OS. I would like to access the internal storage drive so I can put in a ROM and flash. Any help would be greatly appreciated!
Click to expand...
Click to collapse
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot once, put the files you need on internal and then proceed from there.
cmstlist said:
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot custom recovery directly from fastboot, put the files you need on internal and then proceed from there.
Click to expand...
Click to collapse
+1
Maybe try using an OTG cable and usb stick. I just went from CWM to TWRP and saw that there was an option to use otg. I did did a backup to the usb directly and it works great. The inbuild file explorer was also able to browse all the files on the usb stick as well
bk201doesntexist said:
+1
Click to expand...
Click to collapse
You edited my quote to say "then boot custom recovery directly from fastboot". Please don't edit me. It does NOT work if your data partition is fully wiped.
On the Galaxy Nexus if you do a full userdata partition wipe, it CAN'T be written by any custom recovery until you do one full boot cycle into a ROM. The custom recovery will fail to mount the data partition. Booting into a ROM regenerates that partition.
You can see this after unlocking the bootloader, which does a userdata wipe. If you flash custom recovery and try to go straight into custom recovery, it will simply find no writable partition at all. Notice that when you boot into system after a userdata wipe, it commences the boot cycle and then reboots itself one additional time. I suspect that first boot cycle regenerates the userdata partition, and then the second boot cycle continues as normal.
cmstlist said:
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot once, put the files you need on internal and then proceed from there.
Click to expand...
Click to collapse
Thanks for your reply as well as everyone else that has contributed to my thread. I am able to get my device to be in fastboot mode but adb does not detect my device. It states:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If this method does not work, would you suggest me to purchase an OTG usb cable as an alternative?
Adb doesnt work in fastboot mode.
Sent from my i9250
Why don't you just fast boot flash stock and start all over?
Sent from my Nexus 4 using xda premium
olive.knight said:
Thanks for your reply as well as everyone else that has contributed to my thread. I am able to get my device to be in fastboot mode but adb does not detect my device. It states:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If this method does not work, would you suggest me to purchase an OTG usb cable as an alternative?
Click to expand...
Click to collapse
In fastboot mode, you need to use fastboot (not ADB) to flash the stock ROM. Then after regenerating the data partition with one boot cycle, go back into fastboot again and flash custom recovery if you don't still have it.
Never tried it myself, but it should be possible to flash a custom recovery right when you're flashing stock through fastboot. Not through flash-all.sh, but manually flashing system.img, boot.img and userdata.img, unzipped from the update-jop40d.zip file, plus cwm.img or twrp.img, and then boot up normally, or directly to custom recovery to push a rom/root/whatever.
Again, if the device already has the latest bootloader/bb version, there's no need to reflash it. If using flash-all.sh, just comment those out from the script.
Sent from my i9250
bk201doesntexist said:
or directly to custom recovery to push a rom/root/whatever.
Click to expand...
Click to collapse
... except that if the userdata partition was completely wiped, directly to custom recovery will not be able to access the data partition until it's been booted into system once.
cmstlist said:
... except that if the userdata partition was completely wiped, directly to custom recovery will not be able to access the data partition until it's been booted into system once.
Click to expand...
Click to collapse
i stand corrected.
still, how about flashing userdata.img before flashing a custom recovery?
edit: I'm sorry. I must prove you wrong this time. I just finished flashing back to stock with the following steps:
- fastboot erase system
- fastboot erase userdata
- fastboot erase boot
- fastboot erase recovery
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot flash recovery twrp.img
- (manual reboot to recovery on the device)
- adb push ~/workbench/maguro/recovery_flashables/CWM-SuperSU-v0.99.zip /sdcard/
- (flash zip on recovery)
- (reboot system from recovery)
- rooted JOP40D, working fully.
bk201doesntexist said:
i stand corrected.
still, how about flashing userdata.img before flashing a custom recovery?
edit: I'm sorry. I must prove you wrong this time. I just finished flashing back to stock with the following steps:
- fastboot erase system
- fastboot erase userdata
- fastboot erase boot
- fastboot erase recovery
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot flash recovery twrp.img
- (manual reboot to recovery on the device)
- adb push ~/workbench/maguro/recovery_flashables/CWM-SuperSU-v0.99.zip /sdcard/
- (flash zip on recovery)
- (reboot system from recovery)
- rooted JOP40D, working fully.
Click to expand...
Click to collapse
I'm sorry if we have had different experiences, but this is what I have experienced:
- fastboot flash userdata userdata.img
- fastboot flash recovery {CWM or TWRP}
- (manual reboot to recovery on the device)
- Attempt to adb push anything
- Error message (I don't remember exactly what)
- Attempt to mount the data partition from the mounts menu
- Error message
- Boot into the ROM once, then into recovery
- No more error messages
This was my experience both on Galaxy Nexus and Nexus 7 3G.
FWIW, my GNex was bought from WIND Mobile in Canada. I have heard that the Play Store Nexus units are sometimes a bit different (e.g. some have reported that the Play Store Nexus does not wipe userdata after unlocking bootloader).
zephiK said:
Why don't you just fast boot flash stock and start all over?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Oh I definitely want to do this but I don't exactly know how to flash stock in fast boot mode. I don't know how to load the zip file in internal storage. If you could provide me a link or instructions on how to proceed I would gladly appreciate it!
olive.knight said:
Oh I definitely want to do this but I don't exactly know how to flash stock in fast boot mode. I don't know how to load the zip file in internal storage. If you could provide me a link or instructions on how to proceed I would gladly appreciate it!
Click to expand...
Click to collapse
When you flash in fastboot, the files reside on your computer and are flashed over USB to the device.
cmstlist said:
When you flash in fastboot, the files reside on your computer and are flashed over USB to the device.
Click to expand...
Click to collapse
I tried using my computer to command my phone in fastboot mode but my computer keeps stating that the "USB device not recognized" and the cmd continues with < waiting for device >. Are my efforts to revive my phone a lost cause?
Search around for GNex fastboot drivers. And make sure you're using fastboot on the computer, not ADB.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Search around for GNex fastboot drivers. And make sure you're using fastboot on the computer, not ADB.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you and very one else that contributed to my post. With your help and a dash of luck I finally managed to return my phone to working order. Thanks again and happy holidays!!!
Found this question from Googling, and I actually have an easy answer for it:
Load TWRP, connect the phone to your computer (I was on Windows), and you can access your Internal Storage and SD card normally through USB as an attached device.
Hi there,
I stupidly downloaded the latest SlimKat .zip onto my nexus 7, but with the file for my i9300, so obviously it does not boot.
Now, I haven't done this in a while apart from a toolkit, but is there a way to push the file via adb? I can boot into twrp and go Advanced, Adb sideload, but then it doesn't seem to 'complete', and I can't find the device from my computer, despite it showing in fastboot when I am in that mode; it does not in adb.
I know I can wipe to factory image, will that COMPLETELY wipe my device? As in, all my downloaded files, titanium backup etc.? Or just /data? I'd like to backup my internal sdcard if at all possible.
To sum up, wiped /system, but no .zip currently on device. Can I remedy this without losing pictures/titanium backup?
Thank you,
Habylab
habylab said:
Hi there,
I stupidly downloaded the latest SlimKat .zip onto my nexus 7, but with the file for my i9300, so obviously it does not boot.
Now, I haven't done this in a while apart from a toolkit, but is there a way to push the file via adb? I can boot into twrp and go Advanced, Adb sideload, but then it doesn't seem to 'complete', and I can't find the device from my computer, despite it showing in fastboot when I am in that mode; it does not in adb.
I know I can wipe to factory image, will that COMPLETELY wipe my device? As in, all my downloaded files, titanium backup etc.? Or just /data? I'd like to backup my internal sdcard if at all possible.
To sum up, wiped /system, but no .zip currently on device. Can I remedy this without losing pictures/titanium backup?
Thank you,
Habylab
Click to expand...
Click to collapse
A factory reset wipes the data and cache, any changes made to the system will still be there after a factory reset. Flashing the complete factory image will also wipe everything. The userdata.img inside the factory image is what wipes everything. You could flash all the images inside the factory image separately except for the userdata image and your data will stay intact.
If you can see it in fastboot just fastboot flash the system.img and the boot.img. Get the "correct" system.img and boot.img (you have to extract the images from a factory image) and put them inside the platform-tools folder of the sdk, manually put your device in fastboot, plug it in to the computer, shift-right click from inside the platform-tools folder, choose "Open command window here," type fastboot devices and you should see your device, type fastboot flash boot boot.img, hit enter then fastboot flash system system.img hit enter. Type fastboot reboot hit enter and your device should reboot normally! All of your data will still be intact. This might be useful 15 seconds ADB Installer v1.3, I personally have the full sdk installed but I did try the ADB installer on my brother's laptop a few months ago.
Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.
If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.
thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:
Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.
I've been following this guide:
https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591
to try and root my Pixel C. I was initially following a different guide, but I believe I now have:
bootloader-dragon-google_smaug.7900.50.0.img and TWRP_dragon_3.1.0-2.img, loaded through fastboot
I was then able to push
Update.ZIP_PixelC_Ryu_system-vendor-boot_OPP1.zip and SuperSU-v2.79-201612051815.zip to /sdcard/ via adb in TWRP. I then tried to install both, as per the guide.
I was a bit confused when the "flashing system.img... this will take some time" part took no time at all, but it had taken a while to get to that point so I figured maybe the messages were in the wrong order or something. Both said they were successful.
Tried booting to system - just came back to TWRP.
So I thought I'd try to flash the system image back on. But I can't push any files now. Everytime I try, it creates the files then fails and I start getting read-only file system errors
If I try to install update.zip again (the one above), I now get "failed to mount '/data-full' (Device or resource busy)"
So I'm quite stuck at this point. Can't revert to stock image, can't install the new image... any help would be much appreciated!
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
peter73 said:
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
Click to expand...
Click to collapse
I second this ^ except for the fastboot boot twrp.img part. Why do you do that? The first line should be enough.
Was trying to apply the upgrade from Global V11.0.6.0.PEDMIXM to V11.0.7.0.PEDMIXM via Orangefox (Stable) but somehow i did something wrong along the way?
Now my phone will not boot into either recovery nor fastboot. The screen is totally blank. But when i connect the phone to my PC, I can see the deivce is readable by Device Manager as Qualcomm HS-USB QDLoader 9008 (COM5)
So What should I Do next?
Tried using the miflash but keep getting the error from downlaoding the hello packet
Any help is deeply appriciated
I would try to start the recovery from the PC using Fastboot and then firmware (firmware_9.9.3), Rome (xiaomi.eu_multi_MIMAX3_20.1.21_v11-10),
recovery (OrangeFox-R10.0-Stable-nitrogen) and if necessary Magisk (Magisk -v20.3) to flash in exactly this order.
Before full wipe including data and internal memory.
This way I was able to revive my Max 3 in roughly the same situation and have been super satisfied with my phone ever since.
Information without guarantee only because it worked for me, it does not necessarily have to work for you. I'm not a programmer justtried it out of my
gut and in my case it worked. I had nothing to lose anyway.
Alternatieve would have been a paperweight
Start Minimal ADB and Fastboot from the PC
1. adb reboot bootloader
2.fastboot boot recovery recovery.img
3.fastboot flash recovery recovery.img
4. Restart in recovery
5. Full wipe including data and internal memory
6.Flash firmware, Rome, clear cache, reboot into the system
Rename the Orangefox Recovery to recovery and it is best to copy it to the directory of Miniumal ADB Fastboot
Pleasant sideeffect .... I now have an Android 10 - Miui 11 system that works absolutely great
rudiratlos57 said:
I would try to start the recovery from the PC using Fastboot and then firmware (firmware_9.9.3), Rome (xiaomi.eu_multi_MIMAX3_20.1.21_v11-10),
recovery (OrangeFox-R10.0-Stable-nitrogen) and if necessary Magisk (Magisk -v20.3) to flash in exactly this order.
Before full wipe including data and internal memory.
This way I was able to revive my Max 3 in roughly the same situation and have been super satisfied with my phone ever since.
Information without guarantee only because it worked for me, it does not necessarily have to work for you. I'm not a programmer justtried it out of my
gut and in my case it worked. I had nothing to lose anyway.
Alternatieve would have been a paperweight
Start Minimal ADB and Fastboot from the PC
1. adb reboot bootloader
2.fastboot boot recovery recovery.img
3.fastboot flash recovery recovery.img
4. Restart in recovery
5. Full wipe including data and internal memory
6.Flash firmware, Rome, clear cache, reboot into the system
Rename the Orangefox Recovery to recovery and it is best to copy it to the directory of Miniumal ADB Fastboot
Pleasant sideeffect .... I now have an Android 10 - Miui 11 system that works absolutely great
Click to expand...
Click to collapse
Thanks you for your reply. But i could not boot into fastboot, recovery or anyother way and stuck in EDL mode