Related
Hello,
That last night I wanted to flash a new ROM from 4.4 to 5.0.1.
I had some bugs, like my full SD card, therefore i installed nothing like apps or pictures .
So I try to re-flash the ROM again after a factory reset.
But, i can not reflash since it has wipe my SD card ..
So I managed to reconnect my phone and flash a recovery.
However, when I install a ROM (official google, or custom), it no longer detects my SD card
when the flash rom: E: unknown volume for path / sd-ext.
I try everything, I do not know how to repartition as originally my SD card.
I hope she is not dead as impossible to get out of my phone ...
I manage to mount the SD card, but still the sd-ext partition that does not exist ...
I just followed here: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
everything works, but again, the sd-ext partition ..
I manage to get to the bootloader, recovery, I can flash a ROM anyway!
However, when I want to take a picture / install / sms .... I get an error "No SD card" or not avaialble space.
I need your help, since yesterday I have no phone ..
Best Regards,
sleakerz said:
Hello,
That last night I wanted to flash a new ROM from 4.4 to 5.0.1.
I had some bugs, like my full SD card, therefore i installed nothing like apps or pictures .
So I try to re-flash the ROM again after a factory reset.
But, i can not reflash since it has wipe my SD card ..
So I managed to reconnect my phone and flash a recovery.
However, when I install a ROM (official google, or custom), it no longer detects my SD card
when the flash rom: E: unknown volume for path / sd-ext.
I try everything, I do not know how to repartition as originally my SD card.
I hope she is not dead as impossible to get out of my phone ...
I manage to mount the SD card, but still the sd-ext partition that does not exist ...
I just followed here: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
everything works, but again, the sd-ext partition ..
I manage to get to the bootloader, recovery, I can flash a ROM anyway!
However, when I want to take a picture / install / sms .... I get an error "No SD card" or not avaialble space.
I need your help, since yesterday I have no phone ..
Best Regards,
Click to expand...
Click to collapse
Easiest way to solve is just to flash a factory image - follow ALL the instructions on this page: https://developers.google.com/android/nexus/images
Have a read of RootSU's post about file system issues after updating - explains how and why this happens, and how to fix. I would just do the above though, just so you know you're totally back to stock.
http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749
it looks run, I can now see my sd card, install applications ...
However, some problem:
- In aborescence I have : sdcard, then 0 / legacy / OBB
Is it the same for you? Is like this for 5.0?
- When flash: E unknown volume to path sd-ext. Unable to unmount or mount /system, but I was able to boot; and it seems to work ..
- Clean master does not detect anything (unnecessary file or anything ..) Why?
- What recovery do you recommend?
- In storage: Various weighs 5.68gb, but there is nothing on it, how to clean?
sleakerz said:
it looks run, I can now see my sd card, install applications ...
However, some problem:
- In aborescence I have : sdcard, then 0 / legacy / OBB
Is it the same for you? Is like this for 5.0?
- When flash: E unknown volume to path sd-ext. Unable to unmount or mount /system, but I was able to boot; and it seems to work ..
- Clean master does not detect anything (unnecessary file or anything ..) Why?
- What recovery do you recommend?
- In storage: Various weighs 5.68gb, but there is nothing on it, how to clean?
Click to expand...
Click to collapse
- go to general > stick roll-up and find my data loss/recovery thread it explains all the /sdcard quirks
- you don't have sd-ext, that's why. you can't mount /system if its already mounted
- who knows?
- TWRP
- again check my recovery /loss thread and also my "sdcard problems" thread in general. particularly the part about lost Nandroid backups
Your best bet is to read those threads, find any lost backups and wipe storage via TWRP
"you don't have sd-ext, that's why. you can't mount /system if its already mounted"
It is normal ? Or it's a problem ? How can i fix it ?
I don't have any Nandroid backup, mine didn't worked ..
sleakerz said:
"you don't have sd-ext, that's why. you can't mount /system if its already mounted"
It is normal ? Or it's a problem ? How can i fix it ?
I don't have any Nandroid backup, mine didn't worked ..
Click to expand...
Click to collapse
Its normal.
Please find and read those threads.
I'm french, and so i didn't understand all , i'm in which case ?
If i understand well, i just have to wipe "data" partition ?
As you say, i have sdcard\0\0\0
Which one i have to moove ?
sleakerz said:
I'm french, and so i didn't understand all , i'm in which case ?
If i understand well, i just have to wipe "data" partition ?
As you say, i have sdcard\0\0\0
Which one i have to moove ?
Click to expand...
Click to collapse
Go to /data/media/0. That's where everything should be. When you're in /data/media/0, you shouldn't see any more "0" folders. If you do, take everything out of those "0" folders and put it all in /data/media/0
So for example you should have your photos in /data/media/0/DCIM. If you have /data/media/0/0/0/0/DCIM, obviously that is wrong.
Sometimes its easiest to wipe everything a d start fresh so copy any data you want to keep to PC, then flash the 5.0.1 full factory image, wiping your device back to default completely.
I just did this, i flashed a full factory image this morning, it was the same ..
I made a factory, wipe a new ROm, always the same, i made everything, nothing work .
the sdcard is boring me ..
I don't know what to do ..
sleakerz said:
I just did this, i flashed a full factory image this morning, it was the same ..
I made a factory, wipe a new ROm, always the same, i made everything, nothing work .
the sdcard is boring me ..
I don't know what to do ..
Click to expand...
Click to collapse
It can't be the same if you flash the full factory image. Please explain the exact steps you took to flash full factory image.
I downloaded : hammerhead-lrx22c-factory-0f9eda1b.tgz
I unzipped , to get the flash-all.bat script (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701)
I make a factory reset
-- E : unknown volume for path [/sd-ext]
I launch the script : http://i.gyazo.com/177625d0c7f9ba60bc207e39536b0b31.png i've got this ..
What i can do now ?
sleakerz said:
I downloaded : hammerhead-lrx22c-factory-0f9eda1b.tgz
I unzipped , to get the flash-all.bat script (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701)
I make a factory reset
-- E : unknown volume for path [/sd-ext]
I launch the script : http://i.gyazo.com/177625d0c7f9ba60bc207e39536b0b31.png i've got this ..
What i can do now ?
Click to expand...
Click to collapse
Unpack all the .img files and do this
fastboot erase system
fastboot flash system system.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot flash boot boot.img
Read general > sticky roll-up> adb and fastboot.... If you get stuck with that
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
And it's seems to work, like you can see : http://i.gyazo.com/f84948dd6d444a47b114437b8878a314.png
Now i have a factory image, what can i do to use a new ROM / get root and unlock bootloader (if it's not done ?)
sleakerz said:
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
And it's seems to work, like you can see : http://i.gyazo.com/f84948dd6d444a47b114437b8878a314.png
Now i have a factory image, what can i do to use a new ROM / get root and unlock bootloader (if it's not done ?)
Click to expand...
Click to collapse
You didn't do the commands I said. The erase was important
You would need to fastboot flash a custom recovery and either flash a custom ROM from that recovery or flash SuperSU from recovery depending if you want a new ROM or just root
i didn't do the command, but as you can see in the screen, just after "fastboot flash system C:/image-hammerhead-krt16m/system.img"
there is : "erasing system.. OKAY"
So i think it's good no ?
sleakerz said:
i didn't do the command, but as you can see in the screen, just after "fastboot flash system C:/image-hammerhead-krt16m/system.img"
there is : "erasing system.. OKAY"
So i think it's good no ?
Click to expand...
Click to collapse
I just wanted you to do it manually yourself, for userdata
Really thank for your help rootSU !
Now, everything works like a charm : )
sleakerz said:
Really thank for your help rootSU !
Now, everything works like a charm : )
Click to expand...
Click to collapse
Great news. Thanks for letting us know
No SD Card
Sorry if wrong thread but, my problem is:
If I'm in twrp it sees the sdcard and all things on it.
In system it doesn't see the things on the SD card.
Please don't return that I have to do a factory reflash.
If I try to download sth. It gives a toast "No Sd Card" .
I can't take it out because I've got a Nexus 4.
Pls. Help me.
Hello
First of all, I'd like to excuse myself because of my lack of knowledge in all that android stuff and also in english. I got my phone rooted just by following tutorials on internet.
I have a Huawei Ascend Mate 7 MT7-L09. Probalby half a year ago, I have unlocked bootloader and installed CWM-based Recovery v6.0.5.1 and got it rooted.
Not long ago, Huawei released a new version of the EMUI, wich I guess is the Android 6.0 marshmallow thing (logically, I was using the previous version). After downloading, I tried to install it but it would reboot to the CWM everytime I was trying. And then, after booting, the phone would tell me the update failed. It's normal, I know. I needed to install it manualy and etc
BUT instead, by pure ''I don't give a crap what may happend'', I did some big crap.
First of all, in the phone's settings, I did a factory reset. I made a backup of all my files and data before (not in the CWM, but in the phone's tools). After the reset, the phone booted in an old-fashioned android version.There wasn't any keys to go home/back on the bottom of the screen. Because of this, the phone was almost unusable because I had to reboot the phone to leave an app and select another.
I raged and booted to the CWM by pressing the + button and the lock phone button.
I went to Mounts and Storage Menu and did all of this
format /boot
format /system
format /cache
format /data
format /storage/sdcard1
format /data and/data/media (/sdcard)
I did the wipe data/factory reset
I also went to Backup and Restore
I made the
delete from /sdcard
delete from /storage/sdcard1
free unused backup data
choose default backup format
I went in Advenced Menu aswell
I chose
wipe dalvik cache
I think that's it. No wonder why it doesn't work well now LOL...
Later on, I thought I may try to fix it. After reading some stuff, I downloaded a package from the official Huawei website, I think it was with the 5.5.3 EMUI or some sort of. After mounting USB storage to my pc, I put the zip file, wich was not really a zip file because it had a .tar format, it would show me by going to the install zip: Impossible to read format lol. Then I found a package of a rom wich was zip. After putting on the phones storage this zip it would start to install and show installing update and then show me: Installation aborted. Then i gave up and decided to ask some help from pros.
So..... What should I do?
I know my explications are weird, but this is the only way I can describe my problem.
Thank you for reading this long story, and even a bigger one if you help me.
hi,
i don't know cwm recovery.
I suggest you install TWRP recovery , then flash the rom image found here.
(i have installed B571 by this way)
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
regards
tar is another compression format like rar and zip.
If you have the software installed to use terminal commands (ADB) to connect to your phone when it is in so called 'recovery'or 'fastboot' mode you should flash the TWRP recovery image for Mate 7 posted somewhere on the forum for better compatibility. It is basically similar as CWM (clockworkmod) but newer.
In another post here there is a summary of firmwares and in that list is also the 'Twrp Backup' of a fresh installation. That should be downloaded, unpacked and placed in the folder where other/previous backups are stored. To find out where that it is you can create a backup yourself in recovery but only select the 'boot' so the backup is done immediately (and useless) and you can browse your phone to see where to put the downloaded recovery backup.
Next is restoring that backup within recovery.
Personally I would also do a factory reset after that but you should be ready to go after that.
Hello. I've got my oneplus 6 with twrp, magisk, and custom kernel. I am currently on partition B. When i change partition to A on twrp and reboot, my Phone is bootlooping few Times until it changes back to partition B.
My thoughts are that i screwed something in the process of instalation and i don't understand fully the idea and workings of the A/B partition. So i have got a question.
When i want to install update and i want to retain root and kernel and twrp, i Will do:
1.Download full 1gb+ update from xda when it Will be available
2.Reboot into twrp (it Will be on slot B, where i have my system now)
3.Flash rom(it Will flash on A probably? But i Will still be on B for now until next reboot? )
4.Flash twrp as it flashes on both partitions
5.Reboot to recovery (Will be on A partition now?)
6.Flash magisk(it flashes on A?)
7.Flash kernel(it flashes on A?)
8.Reboot to system (i am on A with my updated system now, my bootloop is fixed and there is old, working version of system on partition B?)
9.Repeat the process when new updates are available.
primus19 said:
Hello. I've got my oneplus 6 with twrp, magisk, and custom kernel. I am currently on partition B. When i change partition to A on twrp and reboot, my Phone is bootlooping few Times until it changes back to partition B.
My thoughts are that i screwed something in the process of instalation and i don't understand fully the idea and workings of the A/B partition. So i have got a question.
When i want to install update and i want to retain root and kernel and twrp, i Will do:
1.Download full 1gb+ update from xda when it Will be available
2.Reboot into twrp (it Will be on slot B, where i have my system now)
3.Flash rom(it Will flash on A probably? But i Will still be on B for now until next reboot? )
4.Flash twrp as it flashes on both partitions
5.Reboot to recovery (Will be on A partition now?)
6.Flash magisk(it flashes on A?)
7.Flash kernel(it flashes on A?)
8.Reboot to system (i am on A with my updated system now, my bootloop is fixed and there is old, working version of system on partition B?)
9.Repeat the process when new updates are available.
Click to expand...
Click to collapse
When you flash system partition contained in the zip, recovery change slot.. so:
1) in TWRP flash update zip, it will be flashed in the unused slot (so if you're on A it goes on B and vice versa
2) flash TWRP zip (this is because in full zip you're going to flash even the original boot IMG so you'll lose TWRP if you don't reflash it instantly after the update
3) reboot to recovery, the system will now change partition A to B or B to A obviously depend on what partition you are
4) now you can flash magisk and kernel and whatever you want
5) reboot to system and enjoy
Sent from my OnePlus6 using XDA Labs
Hitman478™ said:
When you flash system partition contained in the zip, recovery change slot.. so:
1) in TWRP flash update zip, it will be flashed in the unused slot (so if you're on A it goes on B and vice versa
2) flash TWRP zip (this is because in full zip you're going to flash even the original boot IMG so you'll lose TWRP if you don't reflash it instantly after the update
3) reboot to recovery, the system will now change partition A to B or B to A obviously depend on what partition you are
4) now you can flash magisk and kernel and whatever you want
5) reboot to system and enjoy
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
Exactly what i wanted to know. Thanks for clarifying that, i forgot to reboot to recovery after flashing it, so it didn't change slot. Now i will remember. Cheers!
Thread can be closed
I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!
Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.
It's caused by no root access
djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!
I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!
https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS
djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.
drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition
Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.
I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes
That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!
Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this
I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!
ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying
Hello guys,
I am looking for help because I am lost.
I have a motorola one vision, its rom is XT1970-3_kane_reteu_RSAS31_48_36_21 according to the lenovo rescue tool
I had flashed XT1970-3_KANE_RETEU_PL_11_RSAS31.Q1-48-36-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml via fastboot
I later was trying to install twrp and magisk to root the phone (to later try to extract data from the userpartition after a factory reset, kind of mission impossible I guess)
I was somehow able to install twrp but later when trying to boot the system the system was simply not there anymore. I must have messed around a bit
I am able to boot in recovery mode to twrp and I need to flash a rom. I would like to reset to factory or to obtain a bootable system and here I am stuck
I have the zip file of XT1970-3_KANE_RETEU_PL_11_RSAS31.Q1-48-36-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip on the external SD card
Currently if I try to boot the system after the logo the phone turns off
I turn on the phone, I get to the bootlooder. I had the bootlocker unlocked. I select recovery mode and enter twrp and here I am stuck:
If I select restore and select storage sd card no file to use for the restore appears in my sd card
If I select install I see the XT1970-3_KANE_RETEU_PL_11_RSAS31.Q1-48-36-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I get invalid zip file format, error installing zip file
Should I use the other zip file? should this rom have another format?
I cannot reflash via fastboot currently
Thanks in advance
May be I have solved:
I saved on the SD card:
lineage-19.1-20220618-nightly-kane-signed.zip
lineage-19.1-20220618-recovery-kane.img
Via twrp I installed the .img file, a recovery tool (the recovery tool will substitute twrp)
(I accessed if I remember well from advanced, install ramdisk or something similar. I did not know exactly what I was doing, intuition was guiding me)
Rebooting the system through the recovery tool I applied the zip file
Later I resetted to factory via the recovery tool.
Once rebooted Lineage OS started in 10m
Now I can eventually reflash the motorola original rom via fastboot