Hi, I bought a new Xiaomi Redmi 5 Pro Global as one of the phones that support MultiRom, to replace my broken LG G3.
For MultiRom I have a Samsung 64GB class10 sdcard that I had partitioned into two partitions, one vfat for data and one ext4 for external roms.
On LG G3 with any Rom I had absolutely no problem having both partitions recognized in recovery mode (naturally I had to use Multirom recovery). But on Whyred only the first partition is recognized in any recovery, and that's a huge problem with MultiRom as I cannot select the second partition to install my external roms.
Moreover, when I try to use the partition SDcard option (only supported in TWRP 3.2.2 and Redwolf), the card is partitioned only into the first partition, and the second one always returns error 134.
I'm very disappointed at that, and I don't know what to do. I tried several roms as primary, MIUI (unfortunately I was stupid enough to let my phone update so I'm stuck only to anti4 roms), RRemix etc, but nothing helps.
Any ideas are welcome, since I even consider selling my phone and it's only two weeks old (I unlocked the bootloader only a few days ago).
Related
Hi,
New to the forum - since I've used so many of the threads to gather new ROMs and sort out problems on my desire, I've decided to share what I've learned. Don't know if this is old news but it's new for me.
Have a rooted Desire and have installed a few different ROMs (opendesire, leedroid, pinkolin's one etc.). Like others, I recently partitioned my SDCARD with one FAT32 and one ext3/4 partition (and a small swap partition) to allow storage of more apps without impacting phone mem too much. Don't ask about swap - old 'nix habits. This worked fine until I tried to install a new ROM recently (went through the Recovery/ClockworkMod method, not ROM Manager).
Thought I had bricked the phone as it booted but got stuck on the loading screen.
Tried wiping all caches/data. No change.
Tried to reflash old ROM and Radio - no luck. ROM installed but same problem.
Tried RUU (including PB99IMG.zip) - no luck. Got CID error.
Noticed that in ClockworkMod, when I tried to mount /sd-ext/ the phone didn't like it - couldn't find the device.
Put SDCARD into a reader and deleted the ext3/4 and swap partitions, then installed the ROM from the FAT32 partition. Phone booted no problem.
Have a hypothesis that, with ext partition present, when ROM is installed, it takes this into account and links the ext partition as a device which then tries to mount as /sd-ext/ which it can't do as it doesn't understand the filesystem until finished booting. Can't mount /sd-ext/ until full boot, can't boot unless /sd-ext/ mounted. Therefore, no booting properly.
With no ext partition present, has to create /sd-ext/ itself and then mounts it which allows full boot into Android.
Would suggest that anyone flashing a new ROM who has an ext partition present either hides or deletes the partition (after backing up apps) to ensure that android doesn't get confused.
Here's a lovely and vague one for you all to try wrap your heads around...
Okay, so I started having trouble with my SD card about a year ago after my mate added a partition so I could flash A2SD ROMs (I believe - I was stuck and asked him to sort it and from what I can gather, that's what he did). It was fine for a while, then suddenly it became nigh on unresponsive to Android: I couldn't take photos, install apps to SD, basically any data transfer between the device and the SD storage was not happening. I think this was after I tried to delete some things to make room for videos and **** but I was stuck on about 300MB of the ~2GB available (this may have been my first attempt to delete after the partition, I'm not sure).
That was the birth of a problem I am still yet to fix. My dad needed a new phone and I wasn't using my Desire anymore. He's 53, and so the Sense UI was less than intuitive to him which lead to me offering to make it a bit simpler for him (flash a stock ROM and use a more information-centric launcher). The device badly needed updating anyways as I hadn't done so since my mate partitioned my SD card and some bugs had began to develop on the ROM I was using. So, I downloaded the latest CM build and set about reformatting the storage to see if I could solve some of the issues. In attempting to do so I think I performed a data, cache and dalvik cache wipe which removed the ROM I was currently using. The partitioning was successful, so I transferred the new ROM and attempted to flash - BOOM! Error message. Tried again, same thing. Now I have a phone that'll only boot into a recovery that's 5 full versions old (CM Recovery v2.5.0.7) without a way to flash an update img. I've tried on many different occasions to try and sort the problem and spent relentless hours trying to research a solution to the numerous different error messages this produces. Every error I can remember was a problem with read/write on the SD card, so I purchased a new one to no avail.
The phone CAN'T be bricked, surely. I still have access to things like USB mounting (which works absolutely fine), and most importantly, access to the recovery. Please don't tell me she won't live on, this is my baby and she's going down fighting! :'(
TL;DR SD card read/write issues. I only have access to recovery. I can mount the SD card via USB in CM Recovery, but every time I try to flash a new ROM I get numerous different read/write errors.
Go here:
http://forum.xda-developers.com/showthread.php?t=1408936
There you can download 4ext recovery that can be flashed via fastboot or using some flasher.
When you flash it repartition your sd card, choose only one sd-ext partition (not bigger than 1,5gb), no swap and fat32 for thevrest of your card.
After repartitioning try to flash some rom and see how it will work.
Hi XDA colleagues,
I am writing this post because I have installed Marshmallow GPE ROM on my M8 and I would like to install the Sense 7 HTC A9 Camera and gallery.
As I have selected my sdcard as Internal Memory, I can't find anymore it under TWRP (2.8.7.0).
And I have see that the /system partition is only 22MB free.
Previously I had a Sense ROM and I don't have used the GPE RUU so my /system partition should not have been resized?
Someone is knowing how is the behavior of TWRP with MM? or maybe a new version is needed?
Many thanks in advance!
Seriously? No reply? Well I'm in the same boat as you, except I have a Moto X pure 2015
Hello,
I have found more details here:
https://www.reddit.com/r/Android/comments/3oz7eu/guidelines_for_marshmallow_users_formatting/
So, formatting SDCard as Internal Memory will crypt it and TWRP will not be able to read it anymore.
You have to rollback to External Memory to gain access again (do a backup of the content before).
Starting with version 3.0.0-0, TWRP has gained the ability to decrypt and mount SD cards that have been migrated to Internal storage under Marshmallow. Of course, the SD card has to be inserted in the device where it was originally encrypted, and I strongly suspect that you would lose the decryption keys if you ever wipe the device.
Your mileage may vary, because there may be some individual devices for which the feature doesn't work perfectly yet. But I can confirm that it appears to work as expected with TWRP 3.0.2-0 on my Galaxy S4.
Hi,
My LG G3 d855 has fried, the flash chip looks dead (unable to flash new system partition, when I try the dmesg from the recovery kernel shows error from the flash chip).
So now I'd like to know if it's possible to install everything on the SD card and boot from there. I already made a copy of all the partitions (I can still read from the flash), the /system partition is unusable but all the other ones look good.
Has anyone tried that ? Or does anyone have an idea where I could stick some boot arguments to make it work ?
I have a UK Redmi Note 8T with 3GB of RAM, 32GB Internal Space and 64GB SD Card - About 6 months ago I managed to unlock the boot loader, install TWRP and install Magisk so it can be rooted. Rooting allowed me to use Airfrozen App to freeze apps from running in the background which helped a lot since this phone only has 3gb of RAM which isn't a lot for Miui - I only have 1GB free of RAM without any apps running.
But last night I think I selected the wrong option in the menu and it seemed to download Miui 11 from the Xiaomi servers and now TWRP and root is gone. Everything looks the same but none of my frozen apps can be unfrozen, unless I go into the google Playstore and do it from there.
I believe my phone in encrypted as when I start it or previously went into TWRP is asked me to draw the pattern to unlock the phone.
Questions
1. If I want to reinstall TWRP will I have to wipe everything off of my phone and start from fresh?
2. Do I have to do some special procedure to install TWRP because it is encrypted? When I installed TWRP 6 months ago I don't remember it being encrypted at the time as I'm sure it didn't ask me to put in my pattern in TWRP - I don't mind wiping my phone and starting from fresh. I just want to use whichever procedure is least likely to brick my phone - even if it means totally resetting the phone and wiping everything.
3. Given I only have 3GB of RAM and 32GB of Internal Space - What ROM would people recommend other than Miui that would run more smoothly and where al sensors like GPS, Camera, etc work as well as in Miui?
4. How is the phone encrypted in the first place? I don't remember selecting any options to encrypt the phone when I first set it up.
Incredible! So far as I know,4g ram is the minimum capacity。
1. reinstall TWRP just flash recovery partion，wipe not necessary，but you have to install magisk or other patch to avoid stock rom change your twrp to original recovery。
2. encrypted just for data partion， but if work abnormally wiping your phone。just backup your imprtant things （ie. precious photos），rom can be reflash from fastboot mode
3. just debloatware，and freeze the apps which you use seldom
4. i think the phone encrypted was the process that check security
sorry for my poor english express...