Can't mount data in recovery, phone is dying - LeEco Le Max 2 Questions & Answers

Can anyone help? My wife's Max 2 is dying, lcd is failing again after replacing it 4 months ago.
It's running aosip Oreo, with TWRP 3.2.1-1 recovery. In settings, the phone indicates it's not encrypted. When I go into recovery and attempt a nandroid backup, I get the dreaded "can't mount data" errors. Also no storage partition to select for the nandroid backup, not sure why that is. I have another Max 2 I'd like to move here system over too if possible.
TIA!

Heyyo, please update to TWRP 3.2.2-0. 3.2.1-1 lacks support for quota storage which is used for a slight boost in storage performance by most Oreo ROMs.
https://twrp.me/leeco/leecolemax2.html
You can use a PC via bootloader with the command
fastboot flash recovery twrp-3.2.2-0.img
Or via TWRP with a USB flash drive mounted and install image to recovery
Or if you're rooted? Flashify app in the play store can also flash to recovery.
Good luck! :good:

can you provide the screen shots?

Related

[CM13 post-MM] Flashing in TWRP auto-reboots phone into recovery - help!

I was running the 8/3 update of Cyanogenmod 13 just fine on my L24. I downloaded the 8/13 nightly from the CM website and tried to flash it, but for some reason it returned error 7, which shouldn't happen because I already updated to EMUI4/MM firmware two weeks ago (as evidenced by me running the 8/3 version with no problems). However, when I then tried to boot back into system, the phone instead booted back into TWRP. Trying to boot into system in any way (from TWRP menu, through bootloader --> fastboot reboot, et cetera) just reboots the phone right into TWRP again. -_-
Now, I can access only TWRP and bootloader, but whenever I try to flash a .zip in TWRP it immediately reboots back into TWRP. I've tried reflashing TWRP (newest version and older versions), flashing the Cyanogenmod recovery for kiwi, factory resetting, and even reflashing the stock recovery and trying to return to stock EMUI. None of these have worked. (And yes, of course I've tried clearing cache/dalvik.)
At this point I'm just looking to actually boot into system...If anyone has any idea how I might be able to fix this, it would be great.
EDIT: to clarify, when I try to flash the ROM in TWRP, I get the following:
updating partition details
full selinux support is present
MTP enabled
and then an immediate reboot. This is very fast - I had to take a video of it and then freeze the frame to see what the message was.
Boot in fastboot and install your crap? Turn phone off connect to your PC hold Power and volume down until it boots.
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
radiobacter said:
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
clsA said:
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
Click to expand...
Click to collapse
Again, the issue is that I can't install any ROM through TWRP, because trying to instantly reboots the phone and brings me back into TWRP. I've tried reflashing TWRP, but it doesn't do anything.
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
radiobacter said:
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
Click to expand...
Click to collapse
The phone is known to be finicky about sd cards. Try formatting it with TWRP
Sent from my SM-N920T using Tapatalk

TWRP Bootloop

Trying to install TWRP to flash a custom ROM, but still without success.
After trying the first few times, holding Vol Up + Power either booted the stock recovery or just booted android.
Then I tried to boot recovery directly through adb commands, and since then recovery is in a bootloop even if I flash TWRP again.
Is there any sollution? I also tried installinh through the TWRP app, but cant flash because it requires root and in order to get rooted I need TWRP...
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
-FliP- said:
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
Click to expand...
Click to collapse
Interesting. Have you tried Androbench?
So which version are You running right now?
Ricky_Karmator said:
So which version are You running right now?
Click to expand...
Click to collapse
I dont even remember to be honest. I think I used the base 3.1 version and got it to detect storage by starting it with the boot adb command. If I run twrp by holding power and vol up, it never detected storage.
I got the same problem with my device X820 6/64 with 19S rom, any TWRP is able to read/write on the internal storage I install TWRP from 3.0 till 3.1.1.1 . What can i do?
Thx
Aj

[URGENT] Flashing Support Needed

[UPDATE]
Hey,
Just to say, I managed to fix the biggest mess up in technology ive done in a long while (thank God). So everything seems to be working fine now.
Thanks
-Rory
Hey,
I recently flashed the Pixel Experience Rom, which automatically activated the "pin at boot" function of Android. That was fine until I tried to root my phone, so booting into TWRP I was greeted with a decrypt screen. I typed in my PIN and it failed. I have reboot my device into TWRP about 6 times now from TWRP as this is a known bug to no avail. Then, panicking, I went on boot loader and ran "fastboot wipe **" (The ** being system, boot, recovery, userdata etc etc). By doing this I stupidly deleted my NAND backup. I then reflashed TWRP. TWRP still needed to be decrypted.
I then used "adb push" to transfer the zip file of the ROM to my phone while in TWRP, I then tried flashing it from TWRP but it returned error code 7 and couldnt mount /system /sdcard etc etc as it had been encrypted.
Right now I am trying to flash the stock firmware from fastboot. I have flashed "system.img" and "boot.img." Yet there is no userdata file.
I have rebooted my phone but it takes me straight to recovery, which is still encrypted.
Any help will be massively appreciated.
Thanks
-Rory
Heyyo, just a heads up format data does a reformat on user data partition and disables encryption.
But I believe I have the proper solution to TWRP in my test thread under BETA downloads as Indian EUI ROM has forced encryption where as Chinese ROMs seem to have none which is why switching from Indian EUI ROM to custom ROMs gives decryption errors.
https://forum.xda-developers.com/le-max-2/development/test-twrp-3-2-1-0-leeco-le-max-2-t3734209

*Urgent* Need clarifications regarding the flashing of TWRP recovery & custom ROMs

*Urgent* Need clarifications regarding the flashing of TWRP recovery & custom ROMs
I want to flash a custom ROM (Pixel Experience Plus) on my Poco/Pocophone F1.
It would be of great help if I get clarifications regarding the following:
1. After unlocking the bootloader, is it necessary to flash TWRP recovery using 'fastboot flash recovery' cmd command, to flash a custom ROM? Or can TWRP recovery just be booted by using the 'fastboot boot' cmd command & then flash the ROM? (This is because I'd prefer to flash a custom ROM without permanently flashing TWRP recovery, I want TWRP temporarily)
2. In case if it's necessary to flash TWRP using 'fastboot flash recovery' cmd command, then do I have to flash DFE (Disable Force Encryption). Can I skip flashing DFE? (Because I don't want to flash DFE & want TWRP temporarily)
3. I want a clean install of the custom ROM. So, can I wipe Dalvilk/ART cache, Data, System, Cache, Internal Storage, SDCard? i.e. everything except, USBOTG (Because, the custom ROM & firmware ZIP files are stored in it & I'll flash them from USB OTG device).
Would this type of wiping affect the TWRP recovery?
4. After wiping everything except USBOTG, can the custom ROM & firmware ZIP files be transferred into the phone's internal storage by connecting it to the PC, while in TWRP recovery?
5. Is it safe to flash the ZIP files from a USB OTG device?
6. As I already mentioned that I want TWRP temporarily (If it's possible). After flashing the firmware & custom ROM. If the recovery is still a stock Mi recovery. Would it affect the functioning of the custom ROM in any way?
If all of the above can be done, is this one of the proper way to flash/boot TWRP recovery & flash a custom ROM? If not, please guide me accordingly.
imegsp said:
I want to flash a custom ROM (Pixel Experience Plus) on my Poco/Pocophone F1.
It would be of great help if I get clarifications regarding the following:.
Click to expand...
Click to collapse
i'm no expert and i'm fairly new to flashing if you're kind enough to read it here's my 2cents.
1) I believe it is necessary to flash with that command & have TWRP as your custom recovery , it is packed with powerful tools. so i don't see a problem not wanting it permanently and it saves you the hassle of flashing it again when changing roms , fixes,etc..
2) Yes , you need to flash the DFE so you won't encounter any errors in TWRP later.
3) " Dalvilk/ART cache, Data, System, Cache " this should be okay , no need to flash everything. for best practices do a factory wipe in TWRP and in advanced mode wipe those 4. make sure to create a backup in-case something goes wrong.
4) I haven't tried this yet , but it seems not doable as you need permission in the phone for the default USB connection toggle if it's in data transfer mode , usb debuggin , charging etc. best is boot your phone then do the transfer in file manager.
5) Yes it is safe since OTG is another form of External Data devices such as SD Card , etc.
6) No it wouldn't affect the rom functionality since rom and recovery is two different thing.. but still , to avoide future mishaps stick with TWRP
you can check this helpful link by madsponge26 : https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
imegsp said:
I want to flash a custom ROM (Pixel Experience Plus) on my Poco/Pocophone F1.
It would be of great help if I get clarifications regarding the following:
1. After unlocking the bootloader, is it necessary to flash TWRP recovery using 'fastboot flash recovery' cmd command, to flash a custom ROM? Or can TWRP recovery just be booted by using the 'fastboot boot' cmd command & then flash the ROM? (This is because I'd prefer to flash a custom ROM without permanently flashing TWRP recovery, I want TWRP temporarily)
2. In case if it's necessary to flash TWRP using 'fastboot flash recovery' cmd command, then do I have to flash DFE (Disable Force Encryption). Can I skip flashing DFE? (Because I don't want to flash DFE & want TWRP temporarily)
3. I want a clean install of the custom ROM. So, can I wipe Dalvilk/ART cache, Data, System, Cache, Internal Storage, SDCard? i.e. everything except, USBOTG (Because, the custom ROM & firmware ZIP files are stored in it & I'll flash them from USB OTG device).
Would this type of wiping affect the TWRP recovery?
4. After wiping everything except USBOTG, can the custom ROM & firmware ZIP files be transferred into the phone's internal storage by connecting it to the PC, while in TWRP recovery?
5. Is it safe to flash the ZIP files from a USB OTG device?
6. As I already mentioned that I want TWRP temporarily (If it's possible). After flashing the firmware & custom ROM. If the recovery is still a stock Mi recovery. Would it affect the functioning of the custom ROM in any way?
If all of the above can be done, is this one of the proper way to flash/boot TWRP recovery & flash a custom ROM? If not, please guide me accordingly.
Click to expand...
Click to collapse
1. if you always want to depend on PC to trigger your Poco in to recovery then use command "fastboot boot recovery.img", otherwise lets say you are on the move and got pixel update! you can simply download it , and flash it in 15 mins on the go , so mainly its upto you . from security point of view, yes its not good to have twrp flashedi n your /recovery , anyone can boot and do harm! , so its a judgement call for you...
2. again upto you, DFE wont interfere/confilt with either rom or twrp
3. android device have various paritition wiping "/system" & "/data" (user setting and apps & appdata) is ENOUGH and called CLEAN FLASHING in various threads of custom roms. you don't have to wipe internal storage!!! you will lose you data... BUT YES if you get encryption error then you must click "FORMAT DATA" button on twrp in order to make storage usable/accessable to twrp. this FORMAT DATA will format your /data /system and /internalStorage partitions and you will delete all your data! then you can flash custom rom of your choice from scratch
4. you don't get access of TWRP FILEMANAGER via fastboot commands from pc, BUT you can do similar by enableing TWRP SIDELOAD option under settings, this adb sideload is a mode listening for new incoming file to flash! if you side load pixelrom.zip from fastboot command while your twrp has active sideload waiting, fastboot will start sending the file and twrp will wait and as soon as the transmit is completed! the file will automatically be flashed!. ,
however you can put files in usbotg drive or combo drive and using file manager in twrp move files from HERE to THERE!
5. I always do it!, but make sure the connection is not faulty!!! otherwise high chances of incomplete flashing and I lost my redmi3i due to impcomplete flashing of stable rom! (bricked)
6. no it wont affect! infact you can even keep the /recovery partition blank! ( fastboot erase recovery).
for MIUI FLASHING/ROOTING / Disabling force encryption etc , this post is king
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
I am on HAVOC2.8 and this is how i did it
1. flashed TWRP 3.3.1 unofficial (download it from HERE ) ref Reference - as official twrp has TOUCH driver issues. this one worked with me very well
2. I wiped /data, /system then
3. flashed VENDOR.zip from HERE
4. FLASHED CUSTOM ROM (i use HAVOC2.8)
5. FLASHED DFE HERE - REFERENCE
6. FLASHED GOOGLE APPS ( GAPPS.ORG) ( ARM64>9.0MicroPackage)
7. Flash Optimus Drunk Kernel ( OPTIONAL- havoc uses shadow kernel , i feel OD kernel is better, battery and 4g connectivity)
8. FLASHING MAGISK19.3
9. when i was on havoc2.7, by using MIGRATE, it made flashable zip of my APPS+DATA, stored in internalStorage, and now I will FLASH that file., Mine size goes to 2gb you can get it from HERE
10. WIPE CACHE/DELVIK
11. REBOOT
fire reboot may go in to bootloop and then second reboot may take a while and finally you should see Pixel Setup asking google accounts and info etc
once after you finish setup! don't RESTORE APPS from PLAYSTORE, (download only license apk, in my case I have purchases many apps from playstore and saperate license info is always appear in intial setup! SELECT THOSE ONLY)
ONCE playstore is DONE downloading all your selected (fewer) apps, and MAGISK ROOT is working...... put device on AIRPLANE MODE
FROM DROP DOWN Notification panel, CLICK MIGRATE, and it will prompt you what do you wana restore from your previouce ROM to newly flashed HAVOC ..APPS+SETTINGS+PERMISSION+DATA etc - migrate restoration may take upto 30 mins,
once done, uninstall from system and reboot device!
REMEMBER I DONOT RECOMEND MIGRATE TRICK FOR WHATSAPP, it doesn't work properly and NOTIFICATION ISSUES with BLANK DP observed by me whenever I forcely re-instated whatsapp by migrate!

HELP! ERROR 1: Using any recovery!

Hi! I have been switching roms weekly to see what rom would be great fit for me.
I was from the device of whyred and certainly curtana is a very different system to mess around with.
Going back to the concern, I cannot flash anything else with any recovery except the original ROM of the device (my device is curtana) and here is what I did so far:
1. Tried format data, restart recovery and then format cache, dalvik, internal - doesn't work
2. Tried changing recovery: LOS, TWRP official, OrangeFox (what I am currently using)
3. Tried changing format partitions (exfat, f2fs, ext4)
I can't do the last resort which is to stay with MIUI because I can't deal with MIUI any longer due to the MIUI apps. (I am heavily reliant to AOSP).
Can anyone help me with this?
First You have to install TWRP recovery and vbmeta with command prompt from fastboot mode, then after installing TWRP, install the Orange fox recovery, enter the new password or pin and format the internal storage, then try two install any rom
If you want any links for files pm me https://t.me/HemanthAryan

Categories

Resources