Develop Bugs

Worst Case and no more ideas (no rom, no recovery)

Hi!
I just tried to change from RCMixHD (D2EXT) to CM7.
As first, I flashed the AlphaRev CM7 image via Android Flasher and right after that the newest radio version via recovery (32.54.00.32U_5.14.05.17). Since the radio is flashed, i was unable to flash anything in recovery mode, so i decided to format everything, wipe all data so that I just lost my current ROM. It still didn't work, so i decided to reflash the Recovery via Android Flasher and now I can't even boot into the recovery menu. For now I can only boot into the HBOOT and use the fastboot. I got Micro-SD adapter to put anything to my SD-Card, but currently i got no idea what to do. Are there any ROMs i can flash with fastboot?
Got any hints to unbrick the recovery?
Current overview of information:
Desire is S-OFF
No current ROM (full data wipe)
Recovery unbootable (stucks at AlphaRev splashscreen)
HBOOT bootable
SD Card formatted with 5,5gb FAT32 and 2gb EXT4
Got Android SDK installed on my computer

Flash CWM 2.5.0.7 or amon ra via fastboot, make sure it's the desire version and md5 matches. Then install a rom.
Sent from my HTC Desire using XDA Premium App

Or go back to stock with RUU for your phone and start again

Thanks for now!
Just flashed the CWM manually with fastboot and i can boot into the recovery again.
However, the recovery is still hanging up when I do any actions related to the sdcard. No update.zip, no manual chooses possible, no wipe.
But for me, it looks like it's not the sdcard which currently ****s up everything, it seems to be the phone itself. I can still mount my sd in recovery, i can also format everything manually, but as soon as i try to install or choose a factory reset, the recovery ends up in a black screen.
--------
edit:
Okay. Looks like i fixed it now by wiping dalvik, battery stats, cache and then wiping data.
Still confused why it works now, but thank you for pushing me into the right direction. Now i can get everything back to work. Thanks!

why hello there!
Has been a while since i had to recover a phone from a worst case scenario, so i thought i could just revive this thread, as there is no desire 310 subforum yet
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment SP_FT_Dump_05-31-2014-12-45-24.zip
Well. That's it. Thanks in advance for anything that may be posted in here
edit:
pictures mentioned above
{
"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"
}

[GUIDE] Install JUI ROM and return to EUI safely

Hello, as everyone knows, the previous JUI beta caused problems with the baseband and EFS partition.
On behalf of a Chinese developer to come out a new beta of JUI that is compatible with our phone, which will detail the steps to install safely.
1: Install this TWRP recovery and make a backup of the EFS partition and save it in a safe place
https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
2: Download the ROM from this link and pass it to the phone and install with TWRP
https://drive.google.com/file/d/0B1WVNNqgsv7lR2d5MDFIdHZYbHM/view
3: After installing, restart your phone and wait for JUI to boot, start with a screen with Chinese letters, after that will restart the phone and start the ROM normally.
EXTRA: GOOGLE PLAY
If you need google apps, follow these simple steps.
1: Dowload BeanGapps
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
2: Install the ROM first, wait for it to start, and when you start to shut down the phone and go to the recovery and install the gapps.
HOW TO GO BACK TO EUI AND REMOVE THE ENCRYPTION
1: Download the latest version of EUI
link here: https://goo.gl/j6A5P4
2: Enter in TWRP recovery and clear all partitions.
3: Move the EUI rom to the memory of your phone and install. Then restart the system and then EUI will start loading, but at the end you will be asked for a password to remove the encryption.
DELETE ENCRYPTION.
1: On your computer, extract the boot.img file from the EUI ROM.
2: dowload TWRP recovery
link here: https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
3: Put the boot.img file and the recovery file in the ADB folder. Then rename the recovery file with this name “recovery.img”
4: Put your phone in fastboot mode, and put these commands in order
PD: Do not forget to move both files to the ADB folder.
1: fastboot flash boot boot.img
2: fastboot flash recovery recovery.img
5: After that, put your phone in recovery mode and go to the wipe section and press “SWIPE TO FACTORY RESET”.
After that a screen appears that says that the phone is encrypted and that it needs to format the partition, and tells it to write YES OR NO,
6: Write YES and clean all partitions.
7: After doing the above, re-install EUI and when you start the phone will no longer be encrypted and will be ready to use again.
screenshots
{
"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"
}
Credits:
@mazapani For uploading the ROM to google drive @SnipHz For the remove encryption tutorial

thanks information and links
I have returned that way and it worked
http://www.leeco.re/topic/1906-helpx720-bricked/

mudur1998 said:
thanks information and links
I have returned that way and it worked
http://www.leeco.re/topic/1906-helpx720-bricked/
Click to expand...
Click to collapse
I can't access this link. Can someone help me, My cool dual C106 bricked, when I plug phone to charger or PC, it only blink red led.

raiso said:
I can't access this link. Can someone help me, My cool dual C106 bricked, when I plug phone to charger or PC, it only blink red led.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=v8eryyvStU8

So if we have twrp installed, do we install eui through it? I thought i read this was dangerous on this phone

LG G3 D852G TWRP/Lineage recovery image 'Primary block device not present'

Greetings.
I have a Canadinan LG D852G from Videotron. I've followed the guides and gotten the phone rooted, and bumped to the point of booting into a new recovery image (TWRP/Lineage) on the phone.
But ... TWRP (and Lineage recovery) can't mount because the primary block device is not present. (So there is no possibility of wiping anything).
I've being going about it like this.
1. Use LGUP to refurbish to lollipop [D852G20d_00_1205.kdz]
2. Root using IMAGEPREP2.6 Direct, and then get SuperSU into PRO mode.
3. Use Imageprep to install KITKAT aboot + laf, and TWRP (Also tried Lineage 18.1 recovery)
I can get into TWRP & lineage recovery, but cannot access internal storage while in recovery. It can't be wiped, formatted or anything.
In TWRP all the partitions are marked as "Present: NO". Lineage recovery has the same issue. (See images)
I've been searching / plunking at it for a few days and I just can't seem to find anything that points to a solution.
With the stock lollipop recovery I can get in and wipe the cache and data/factory reset and the logs show successful completion. It's not encrypted either.
I've also been unable to get a complete working KITKAT KDZ/TOT for my specific device, so I can't start from a complete factory KITKAT install. [ The only D852G Kitkat .tot I found just caused a bootloop, and I had to hard unbrick using BoardDiag ... That was a fun learning experience. ]
I'm stumped and still digging for more info. I am very new to android, but have plunked around many years ago with Gentoo so I have a small amount of familiarity with linux.
Does anyone have any hints or tips, or knows what the heck I'm doing wrong, any help would be greatly appreciated.
Thanks!
{
"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"
}

Fractux said:
Greetings.
I have a Canadinan LG D852G from Videotron. I've followed the guides and gotten the phone rooted, and bumped to the point of booting into a new recovery image (TWRP/Lineage) on the phone.
But ... TWRP (and Lineage recovery) can't mount because the primary block device is not present. (So there is no possibility of wiping anything).
I've being going about it like this.
1. Use LGUP to refurbish to lollipop [D852G20d_00_1205.kdz]
2. Root using IMAGEPREP2.6 Direct, and then get SuperSU into PRO mode.
3. Use Imageprep to install KITKAT aboot + laf, and TWRP (Also tried Lineage 18.1 recovery)
I can get into TWRP & lineage recovery, but cannot access internal storage while in recovery. It can't be wiped, formatted or anything.
In TWRP all the partitions are marked as "Present: NO". Lineage recovery has the same issue. (See images)
I've been searching / plunking at it for a few days and I just can't seem to find anything that points to a solution.
With the stock lollipop recovery I can get in and wipe the cache and data/factory reset and the logs show successful completion. It's not encrypted either.
I've also been unable to get a complete working KITKAT KDZ/TOT for my specific device, so I can't start from a complete factory KITKAT install. [ The only D852G Kitkat .tot I found just caused a bootloop, and I had to hard unbrick using BoardDiag ... That was a fun learning experience. ]
I'm stumped and still digging for more info. I am very new to android, but have plunked around many years ago with Gentoo so I have a small amount of familiarity with linux.
Does anyone have any hints or tips, or knows what the heck I'm doing wrong, any help would be greatly appreciated.
Thanks!
View attachment 5368591View attachment 5368593View attachment 5368595
Click to expand...
Click to collapse
Sent you a pm.

Question [URGENT] Failed to mount '/system_ext' '/product' '/vendor' '/odm' (Invalid argument)

Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"

Pillow fan said:
Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"
Click to expand...
Click to collapse
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...

reg66 said:
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...
Click to expand...
Click to collapse
I just controlled and it seems what i did while trying to flash the fastboot rom is completely wrong since i tried to flash the recovery version. I have downloaded the fastboot rom now but i will have to try to install it tomorrow

The rom was flashed succesfully this time but it still goes into the mi recovery when trying to boot. i flashed twrp to see if i could flash the rom from there and now all partitions can be mounted except for /data. When trying to decrypt it using the pin passcode it says Password Failed. is it because i also had the fingerprint and face unlock? When i still couldn't mount the other partitions I always used the pin passcode to decrypt storage. Has the passcode been changed when flashing with the mi flash tool? I don't have a recent system and data backup nor a backup of the internal storage so this issue is devastating to me, i want to save my data at all costs
EDIT: I tried reflashing twrp from fastboot and now I also can't mount the /cust partition with error "Structure needs Cleaning"

Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first

reg66 said:
Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first
Click to expand...
Click to collapse
So i have to accept that all my data is gone? No chances of decrypting the data partition? I'll wait and see if someone has something that could work, if nothing else does i guess i'll have to accept the reality. Thank you anyway

I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting

Sauceunny said:
I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting
Click to expand...
Click to collapse
TWRP doesn't display the "OS not installed error" and before flashing the fastboot rom version the data partition could be decrypted normally with the lockscreen passcode. Does this mean that Mi Flash encrypted the data partition with a different key?

Thank you to @reg66 and @Sauceunny , I have decide to wipe the memory of the phone as i have deemed it to be too much work to save some chats and images while the most important files are stored as a backup. I will have to plan the next update or changing rom more thorougly next time.

I have the same problem with my S21 ultra
Error on product, vendor and ODM
So i can't install stock ROM because of this error.
Doesnl anyone have an idea?

{
"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"
}
i cant mount system
i use poco f3
cant someone help me for fixed
how tp fixed..
please help

I'm facing the same errors except "Odm" I don't know what to do I tried to flash pixel experience rom in my mom's redmi note 10 using "twrp" it's just just in it. Please help me out

Download fastboot rom, use miflash to flash it (select clean all without lock) and dont play with mom's phone again. Watch a miflash tutorial on youtube if you're new to this.

Trying to install Kali Nethunter on OnePlus 7T unable to mount partitions error

Hello thanks for reading,
I've spent about 2 days trying to figure this one out so any help would be greatly appreciated.
I've flashed it back to stock rom "hotdogb_14_O.22_210127.ops" with the MSM tool and flashed recovery TWRP to it, but I am consistently receiving the error
" Failed to mount '/system_ext' (Block device required)" in TWRP when i'm trying to write zip files and disable encryption.
when it comes to install anything, I get this same message and it fails - where am I going wrong? i've tried wiping it and repair as ext4 but nothing, same deal... any ideas?
Thanks in advance

tehnooks said:
Hello thanks for reading,
I've spent about 2 days trying to figure this one out so any help would be greatly appreciated.
I've flashed it back to stock rom "hotdogb_14_O.22_210127.ops" with the MSM tool and flashed recovery TWRP to it, but I am consistently receiving the error
" Failed to mount '/system_ext' (Block device required)" in TWRP when i'm trying to write zip files and disable encryption.
when it comes to install anything, I get this same message and it fails - where am I going wrong? i've tried wiping it and repair as ext4 but nothing, same deal... any ideas?
Thanks in advance
Click to expand...
Click to collapse
Use twrp v1 on twrp.me ?
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me

HueyT said:
Use twrp v1 on twrp.me ?
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
Click to expand...
Click to collapse
Giving it a try right now, fingers crossed, I used a different version that boots before but not this one it seems. I'll let you know
Thanks for your time replying

Use twrp v1 on twrp.me ?
HueyT said:
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
Click to expand...
Click to collapse
Didn't work, same issues, i'm at my wits end someone help me pretty please! Here's a screenshot
{
"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"
}
Does this no matter what I install, even if I go to format and wipe data always fails at that point, what command or trick am I missing guys? *begs*

Bootloader unlocked?

HueyT said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yeah, all unlocked and ready to go else wouldnt let me boot into twrp without that first. I tried it with the latest version of android 11 and it didn't have the same message but still gave me a cant mount /opm (or something close to this) error message.... I feel like its something simple that I just lack the knowledge of

tehnooks said:
Yeah, all unlocked and ready to go else wouldnt let me boot into twrp without that first. I tried it with the latest version of android 11 and it didn't have the same message but still gave me a cant mount /opm (or something close to this) error message.... I feel like its something simple that I just lack the knowledge of
Click to expand...
Click to collapse
Did u "mount data" while in twrp before formatting data?

Morning Huey, No I did not, I am about to try it again right now just restoring via MSM and i'll give it a go
I've been following the guide at https://www.kali.org/docs/nethunter/installing-nethunter-on-the-oneplus-7/
but it's not for the 7T so maybe theres something missing, ive even tried using the older versions they suggest on there with no luck so far

HueyT said:
Did u "mount data" while in twrp before formatting data?
Click to expand...
Click to collapse
doesn't let me mount data before formatting data ;(

tehnooks said:
doesn't let me mount data before formatting data ;(
Click to expand...
Click to collapse
Remove screenlock before rebooting into twrp as your twrp is not decrypting data on 11.0.9.1

I'm downgraded to the last android 10 version as the guide says (but for hotdog) but always get the same error no matter what, I never set a screenlock or password or even a fingerprint, will update to 11 and latest update and try it again but it said can't mount /opm or something similar doing it that way. I feel like i'm just missing something really simple about the whole thing but i've followed the guides to a T