So I had flashed a treble ROM (9.0) with red wolf recovery but after that red wolf recovery started asking for a password but I didn't set any password and after formatting my whole device using the recovery it is reading the internal storage at the same boot but after one reboot red wolf is still not reading the internal storage what should I do?
Wipe data
mt
Tyrese117 said:
Wipe data
Click to expand...
Click to collapse
After I wipe the data I am able see my internal storage but after rebooting in the recovery mode again I am unable to see my internal storage once again
coder.amit said:
So I had flashed a treble ROM (9.0) with red wolf recovery but after that red wolf recovery started asking for a password but I didn't set any password and after formatting my whole device using the recovery it is reading the internal storage at the same boot but after one reboot red wolf is still not reading the internal storage what should I do?
Click to expand...
Click to collapse
Hi, flash twrp recovery from your PC. I had the problem too.
Wipe all data, flash redwolf and rom after.
Related
ok. so i was running medroid 6.1 on my nexus fine, then i went to go update it to medroidmodremix 1.2.1 and i wiped dalvic cache but not user data.. first it would not even turn on, then i booted into recovery and i fully wiped everything cache, dalvic, system data, user data etc.. then i got boot loops on the medroid boot logo. it would restart after 10 mins and boot loop again. i then booted into recovery and deleted everything and wiped dalvic cache and updated to medroid 1.3. and it still is boot looping..
please help
ps: it gets pass the x logo but loops at the medroid logo and reboots.
Normally, it would reboot three times at the X logo after wiping dalvik since it has to move it back to sd-ext, but since it's looping at the medroid logo, something else is amiss.
My first guess would be that you might have to repartition your sdcard. There shouldn't be any problems with your hboot partition scheme as it would have looped at the X logo if that was the problem.
Thanks for the reply.
and im kinda a n00b at this stuff.. How would I partition my sd card. I tried doing it with the recovery in my nexus but it always fails.. im running windows 7.
harjnijh said:
and im kinda a n00b at this stuff.. How would I partition my sd card. I tried doing it with the recovery in my nexus but it always fails.. im running windows 7.
Click to expand...
Click to collapse
Do like this:
1. Download and flash 4ext recovery. It's pretty much the only recovery to actually make good partitions.
2. Boot into the recovery.
3. Mount USB storage and connect your phone to your PC
4. Copy-paste everything from your sdcard to your PC
5. Unmount the USB storage and enter the partition menu and partition to ext2. Choose 512mb for the first partition, 0mb for swap and 0mb for the second partition and leave the rest for fat (or fat 32)
6. Now mount USB storage again and this time copy-paste everything back to your sdcard.
That should do it.
Oh, and download and install this .apk to automatically download 4ext recovery and future versions of it. It's the free and somewhat limited version. There is a paid version in the market for all features.
http://www.4ext.net/get.php?apk
how do i flash 4ext recovery when my nexus doesnt turn on?
how do i flash 4ext recovery my nexus doesnt get past medroid logo.
harjnijh said:
how do i flash 4ext recovery my nexus doesnt get past medroid logo.
Click to expand...
Click to collapse
Ah, worry not! Simply reboot your phone into fastboot mode and plug your phone to your computer. Make sure you have ADB set up correctly and fastboot drivers installed.
Then go to the folder where you have a fastboot.exe and shift-right click and select open command windowd here. Then make sure you have your recovery in that folder and the type:
fastboot flash recovery name-of-recovery.img
fastboot reboot-bootloader
where to download
where can i download the recovery from. 4ext is a .apk. please provide link
harjnijh said:
where can i download the recovery from. 4ext is a .apk. please provide link
Click to expand...
Click to collapse
http://nexusone-medroid-ics.googlecode.com/files/4ext-recovery-RC3.img
thanks man !!!
thanks man you the best!!!!!!!!
it worked!!
harjnijh said:
thanks man you the best!!!!!!!!
it worked!!
Click to expand...
Click to collapse
You're very welcome!
Hey guys,
My work switched to Google Apps for their email so i wanted to test it out on my phone. Doing so required them to encrypt my phone. What this appears to have done is encrypt the data partition. So now when i go into (TWRP) recovery and try to do a backup / wipe / or anything else, it says it is "Unable to mount /sdcard" I'm unable to do a factory reset of any kind so i'm essentially stuck on this rom (ARHD) until i can figure out how to wipe data and get the /sdcard to be not encrypted. Does anyone have any ideas? I'm imagining that with the modified recovery not being able to access the data partition that i'm going to have to do some adb type stuff?
Please help! I want to keep flashing new roms!
Anyone??
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Guich said:
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Click to expand...
Click to collapse
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
jrun said:
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
Click to expand...
Click to collapse
Hi! Only TWRP recovery can solve your issue just do this...
Boot to TWRP recovery->Wipe
From there there are 2 options the left is the advance wipe and on the right is Format Data
Just select the format data button and it should reformat the whole data partition.
1st one would prompt so many errors and reformat then reformat it again 1 time and it should fully reformat your phone.
In theory it should reformat data partition even when encrypted but just in case it fails and I won't be able to go back to this thread just boot in bootloader and type
"fastboot erase userdata"
Well none of that works. TWRP doesn't support decryption yet for this device.
sevenalive said:
Well none of that works. TWRP doesn't support decryption yet for this device.
Click to expand...
Click to collapse
What I instructed basically doesn't decrypt the partition. It reformats it.
Riyal said:
What I instructed basically doesn't decrypt the partition. It reformats it.
Click to expand...
Click to collapse
I know what you instructed, it doesn't work. Only way I got it to work. Flash the stock recovery. Boot into system. Take off the encryption, phone reboots and removes the encryption, data is formatted. Then flash TWRP again.
I basically ran into this exact problem. I was hoping that I'd still be able to back up the encrypted device, but forget about it. What a pain in the ass.
Someone should make add something to the guides about how encrypting your device makes nandroid backups impossible.
Hi i have a problem with my galaxy note, i rooted my phone with philz touch 5 and i was trying to install a kitkat rom
and it was giving me an error, after a lot of research i found that i needed a newer version of cwm so i found philz touch 6.25
i went to my sd card and dropped the thing there and i installed it with install zip from sd card.
after that i installed asylum rom and when i rebooted it stuck on boot screen,went back to cwm and did factory wipe started again nothing ,
installed new rom this time slimkat again stuck on boot screen after that lightning rom nothing stuck tried stock rom with odin nothing agin when i start my phone it stays on cyanogenmod boot screen.
can anyone help me im new to this stuff
sorry for my english
and thanks
Flash raw r4 kernel from recovery. Then reboot into recovery. Go to mounts and storage and format system, data and cache. Then flash the new rom.
nokiamodeln91 said:
Flash raw r4 kernel from recovery. Then reboot into recovery. Go to mounts and storage and format system, data and cache. Then flash the new rom.
Click to expand...
Click to collapse
here is what i did
1.downloaded raw r4 kernel and add to sd card
2.boot to philz recovery install raw r4 kernel
3.reboot to recovery now is CWM-BASED RECOVERY V6.0.4.4
4.went to mounts and storage and format system data cache
5.installed sweetrom v11.1_LTA rebooted
6.stuck on boot screen
7.tested omni rom again the same it stays on boot screen
when i try to install from the sd card i see that there is an extra partition sd card0 and sd card1 on the first partition it contains lost dir,twrp/,clockwokmod and the other one my roms shouldnt be only one????
any other idea?
One is your internal and other is external sd. When you say stuck on boot screen? What exactly do you see? The Samsung flashing logo? Of that then it takes a while to boot.
tsehos said:
here is what i did
1.downloaded raw r4 kernel and add to sd card
2.boot to philz recovery install raw r4 kernel
3.reboot to recovery now is CWM-BASED RECOVERY V6.0.4.4
4.went to mounts and storage and format system data cache
5.installed sweetrom v11.1_LTA rebooted
6.stuck on boot screen
7.tested omni rom again the same it stays on boot screen
when i try to install from the sd card i see that there is an extra partition sd card0 and sd card1 on the first partition it contains lost dir,twrp/,clockwokmod and the other one my roms shouldnt be only one????
any other idea?
Click to expand...
Click to collapse
update
i tried again flashing a stock rom usin odin once it finished it went to boot logo and after 20 seconds the logo restarted all it does is restarting the samsung logo,i went to recovery and it shows a dead android and with red letters E: failed to mount /efs (invalid argument) tried factory reset nothing.
Failed to mount efs? Hmm.. Check in your internal sd card if you have any file named efs backup or efs auto backup of 20 MB in size?
nokiamodeln91 said:
Failed to mount efs? Hmm.. Check in your internal sd card if you have any file named efs backup or efs auto backup of 20 MB in size?
Click to expand...
Click to collapse
how do i do that i can only mount ext sd card in cwm and and when i go to mounts and storage and try to mount efs i get error mounting efs and i dont have a back up for that
tsehos said:
here is what i did
1.downloaded raw r4 kernel and add to sd card
2.boot to philz recovery install raw r4 kernel
3.reboot to recovery now is CWM-BASED RECOVERY V6.0.4.4
4.went to mounts and storage and format system data cache
5.installed sweetrom v11.1_LTA rebooted
6.stuck on boot screen
7.tested omni rom again the same it stays on boot screen
when i try to install from the sd card i see that there is an extra partition sd card0 and sd card1 on the first partition it contains lost dir,twrp/,clockwokmod and the other one my roms shouldnt be only one????
any other idea?
Click to expand...
Click to collapse
Sorry I think you are confused...You have flashed raw kernel for 4.4 roms, then you've installed sweetrom that is 4.1...I'm sure that you stuck on boot. Search for a 4.4x rom, flash raw kernel and you'll see will work. with raw, internal sdcard is /emmc. If you want to install sweetrom you have to flash Philz kernel. See roms threads.
jsdroid said:
Sorry I think you are confused...You have flashed raw kernel for 4.4 roms, then you've installed sweetrom that is 4.1...I'm sure that you stuck on boot. Search for a 4.4x rom, flash raw kernel and you'll see will work. with raw, internal sdcard is /emmc. If you want to install sweetrom you have to flash Philz kernel. See roms threads.
Click to expand...
Click to collapse
i tried with slimkat and asylum omni both are 4.4 and its the same problem somehow i messed up and now i flashed a stock rom with odin
and it stuck samsung logo and when i go into recovery it gives me with red letter e:failed to mount efs i read somewhere that i have to take to samsung service to fix if its possible
Flash PhilZ kernel again and then flash aroma file manager to check if there is an efs backup in the internal storage.
nokiamodeln91 said:
Flash PhilZ kernel again and then flash aroma file manager to check if there is an efs backup in the internal storage.
Click to expand...
Click to collapse
done but there a lot of files i can only look in root do you know where to look exactly?????
tsehos said:
done but there a lot of files i can only look in root do you know where to look exactly?????
Click to expand...
Click to collapse
Usually stored in the root of internal SD,, also in clockworkmod folder.
nokiamodeln91 said:
Usually stored in the root of internal SD,, also in clockworkmod folder.
Click to expand...
Click to collapse
internal sd 0 files
the clockworkmod is in sdcard and there is only a screenshots folder
i have searched a little bit but i dont see the file
tsehos said:
internal sd 0 files
the clockworkmod is in sdcard and there is only a screenshots folder
i have searched a little bit but i dont see the file
Click to expand...
Click to collapse
update i have followed this and tried it on my phone and it works but i have to check
if there is a problem with my imei i can make calls send messages and everything
here is the guide http://www.youtube.com/watch?v=xJMJLdzHaAY please watch and tell me if there
will be a problem with something
Try wipeing data and cache after flashing stock rom via odin
tsehos said:
update
i tried again flashing a stock rom usin odin once it finished it went to boot logo and after 20 seconds the logo restarted all it does is restarting the samsung logo,i went to recovery and it shows a dead android and with red letters E: failed to mount /efs (invalid argument) tried factory reset nothing.
Click to expand...
Click to collapse
after flashing with odin you should wipe data and cache then reboot!
I was running TWRP 3.1.1 on my Redmi 4x and i decided to update it to TWRP 3.2.1
I installed the TWRP 3.2.1 by going to recovery>install>install boot image>then install to recovery partition
After i installed it and i booted to recovery, it's already updated to TWRP 3.2.1 but my pattern for twrp is not accepted. Whenever i enter my pattern it will have an error that is failed to decrypt because of a wrong pattern. I didnt even change my pattern from 3.1.1 but somehow when i updated to 3.2.1 my pattern is not accepted.
So now i cant decrypt the internal storage.
Help please
Lancer43 said:
I was running TWRP 3.1.1 on my Redmi 4x and i decided to update it to TWRP 3.2.1
I installed the TWRP 3.2.1 by going to recovery>install>install boot image>then install to recovery partition
After i installed it and i booted to recovery, it's already updated to TWRP 3.2.1 but my pattern for twrp is not accepted. Whenever i enter my pattern it will have an error that is failed to decrypt because of a wrong pattern. I didnt even change my pattern from 3.1.1 but somehow when i updated to 3.2.1 my pattern is not accepted.
So now i cant decrypt the internal storage.
Help please
Click to expand...
Click to collapse
Press back button on the page where twrp is asking for patter then go to wipe then format your data . This should solve the issue .
rkdok23 said:
Press back button on the page where twrp is asking for patter then go to wipe then format your data . This should solve the issue .
Click to expand...
Click to collapse
Is there any other way that wouldnt require me to format my data?
Lancer43 said:
Is there any other way that wouldnt require me to format my data?
Click to expand...
Click to collapse
Enter twrp. After that press back button,, enable mtp on mount. And connect your phone to ext storage. Backup your files and rom. After backup. Just format it,,,
Important: backup rom first than files
MattHdH said:
Enter twrp. After that press back button,, enable mtp on mount. And connect your phone to ext storage. Backup your files and rom. After backup. Just format it,,,
Important: backup rom first than files
Click to expand...
Click to collapse
How can be data accessed through mtp when partition is not mounted because it is not decrypted ?
There is an akward situation, whenever i try to go into TWRP for flash any zip aur img file , TWRP does not show any such file. It is 100% sure that i transfer the flasheable zip file to the mido. But TWRP does not show. It shows 0mb internal storage. And i tried to wipe delvik cashe data system but it gives a message and error in red color that data not mount.
So for this i just formate the phone by twrp... It get easly formate by typing YES and delete all the internal storage, after that i can wipe all the stuff under advanced wipe by selecting all the options system data delvik cashe.... Etc.
After doing this i just power off the phone by twrp, and again boot the phone into twrp recovery by pressing volume up+ power button
And then twrp shows 52 gb aprx internal , so i transfer the custom rom zip file and gapps zip to the phone using computer.
After that i had flash the rom and reboot the phone into system..
The phone get started and work awsome.
Now after an hour latter , i had again reboot the device to recovery ... To flash magisk manager ... Guys i am shoked the internal storage shows 0 mb instead of actual memory.
Again does not shows any zip file, img file.
So i have to follow all the steps that i performed before formate the phone and reboot to recovery then transfer magisk and then flash it.
The problem is why twrp again and again shows 0mb error ...
So i also flash the miui using fastboot method (clear all) clean flash, then flash the twrp after that flash the custom rom.
After flashing rom , Now again reboot to recovery it shows 0 mb internal and data unable to mount.
Twrp fix temporary not permanent.
Please tell me if you find any solution for this for permanant fix twrp 0 mb error....
dheerajsinghal said:
Please tell me if you find any solution for this for permanant fix twrp 0 mb error....
Click to expand...
Click to collapse
Wrong section here.
https://forum.xda-developers.com/redmi-note-4
Hi! actually i had similar issue after restoring all partitions (not just boot data and system, but all the 10 or more partitons) on my redmi 4x. i couldnt mount the data partition it got corrupted somehow. I couldnt format it in twrp too. Reflashing everything in my flash solved the problem, just dont forget to NOT choose the option with RELOCK, or you will lock the bootloader.