Related
About a month ago my Xoom (MZ605, EOS 3.0) froze and I had to do a hard reset. After that the tablet became unusable due to the neverending stream of Closed Force dialogs. First I thought the fs and or partition table were buggered, but now I have discovered that whatever I do to the emmc, nothing changes at all: Fastboot flash, SBF flashing, fsck and gdisk in recovery (using adb shell). In all cases, the writing and flashing completes without any errors, but when checking for the results, nothing has changed at all.
Any idea on what might have caused this? Or even better: how to make to emmc writable again? If necessary I'm willing to open it up and mess with the hardware.
Thanks!
Have you tried locking and then re-unlocking the boot loader? Just a suggestion, not promising anything.
It will, normally, wipe your internal storage so make sure you backup any necessary data to a computer.
Sent from my SAMSUNG-SGH-I747 using xda premium
Hi d3athsd00r,
I tried that several times, but just be sure I tried it again. Unfortunately it didnt help Thanks for the suggestion anyway! If you or anyone else has any other ideas, please let me know. The personal data on the tablet isn't important btw (just music), so there's no problem if everything is lost.
Have you tried to format everything in cwm under the mounts menu? (Remove sdcard before doing so)
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.
ioish said:
I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.
Click to expand...
Click to collapse
I would say your recovery is faulty. Try an earlier version or a different kind
Sent from my Xoom
Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.
ioish said:
Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.
Click to expand...
Click to collapse
odd indeed....have u looked to see if any other devices from other makes have had a similar issue?
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
I looked a lot on google, but didn't find anything relevant to my case. I even tried to find the datasheet of the chip to if there's a pin (ball) that controls the read-only, like a switch would. Unfortunately it doesn't seem to be publicly available on the internet.
The only topics I found to remotely relevant is:
http://discussions.nokia.com/t5/Maemo-and-MeeGo-Devices/Memory-In-Readonly-Cannot-Flash-EMMC/td-p/1030885
bu that doesn't have any relevant info.
Are you familiar with linux?
If you are, check out the first post on page 2 of this thread.
http://forum.xda-developers.com/showthread.php?t=1609825&page=2
Sent from my SGH-I747 using xda premium
Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.
ioish said:
Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.
Click to expand...
Click to collapse
Very odd indeed. I might have missed this but have you tried installing CWM (not TWRP as it only does the rm) and attempting to do a format from there?
Sent from my SGH-I747 using xda premium
I did try installing CWM using fastboot flash and also a newer version of TWRP and the command completes succesfully, no errors on the screen. When booting into recovery, the same TWRP is still there, as if I never flashed anything
Same problem with my Moto G. Nothing gets flashed. emmc is just write protected and I cannot mount anything
Hi All,
I have a Samsung Galaxy S2 LTE (SGH-I727R, but the same as the SGH-I727) and was wondering how a guy would go about re-partitioning the internal storage on the phone.
The phone has 16gb of internal memory. This has been partitioned, from what I can see, into 2gb and 12gb. The 2gb 'system' partition where your OS and apps, etc are installed and the 12gb storage partition for things like photos, music, movies, etc.
I don't store anything on my phone, mostly just photos. So i have approximately 9gb of the 12gb of the 'storage' partition available. However, the 'system' partition is pretty much maxed out. I'm running Vincom's Superlite CM10.2 rom with minimal apps installed, but it says that i only have around 160mb available and I've begun to received the 'low storage space' error/notification.
I understand that I can use Odin to re-partition the device but that I require .pit files in order to do so. Furthermore, the stock .pit files wouldn't change the size of the partitions. Ideally I'd like to increase the size of my 'system' partition and reduce the size of my 'storage' partition.
Can anyone out there help me? Please let me know if you need more info from my device.
That's not gonna happen
Sent from my HTC One using Tapatalk
how come?
messing around with the partitions will most likely hardbrick the device so no one would ever try doing it, the only way your system partition is filling up is if you are manually installing apps into that partition or the partition is messed up, odin back to stock, then wipe everything including preload then do a fresh install of a custom rom
Will do, I'll update later with results. It's weird though, i haven't manually changed the default installation locations for apps, they just automatically install there. I'll wipe and format everything, odin back to stock, flash the latest version of TWRP and then flash SL CM10.2 and let you know.
Thanks for the help Vincom.
PS - Great roms, thank you for the contributions to the community!
Odin'd back to stock, wiped everything (cache, dalvik, system, data, android secure), formatted USB storage, Odin'd TWRP 2.6.3.0 - everything went fine in that respect.
Booted into recovery, went to flash SL CM10.2 (i dropped these in 'external_sd' after formatting usb storage) and got the following error during the 'making sure you really do have the skyrocket and jb radio' sequence:
'assert failed: run_program (" /tmp/test_radio_vers
E:error executing updated binary in zip '/sdcard
Error flashing zip '/sdcard/external_sd/CM-10.2_
Updating partition deatils...'
Seeing as how I'm attempting to flash from stock rom (which was a GB rom) does it matter that the test sequence is looking for a JB radio?
Thoughts?
also noticed that it won't let me wipe 'data' in TWRP... says failed, with the error 'unable to wipe /data'
rebooted into recovery and now it will let me wipe 'data'....wtf is going on with my phone?
you need todo more reading as u need jb radio or else it will not install cm10.2+ and post an error and sometimes after the error twrp should be rebooted to properly unmount/mount partitions, i think the phone is fine, but the user is another matter..........
i guess i didn't really flash a custom rom until after i upgraded to the Rogers release of JB...? Can't remember... anyhoo, could I simply flash your SL Rogers JB 4.1.2 to obtain the JB radio and then flash SL CM10.2?
Or is there a flashable zip for the radios? I could have sword I saw those some place, but i can't find them now...
banghead
|Read This b4 posting | THE MOST Common Questions Answered HERE | its a sticky right above ur post
thanks for acknowledging/tolerating my stupidity/ignorance, both the 'read this before you post' and '1 stop' threads were helpful.
i did have one more perhaps stupid question that wasn't answer in either of those threads (or at least that I could find), I got SL CM10.2 up and running...bare bones. When checking storage in the settings app, it told me that my total space was 1.97gb and that i had 1.92gb free.... cool. I then rebooted into recovery and flashed gapps lite (12mb) and email/exchange. Rebooted my phone, checked my storage and now i have 432mb free...? This is exactly where i started... i have no apps other than what came with SL CM10.2, gapps lite and email/exchange and only have 432mb available.... any ideas as to what's going on here?
comparatively, i checked my 'apps' in settings, the 'downloaded' tab has nothing, the 'on sd card' tab has nothing, and the 'all' tab indicates that i've used 1.5gb of my internal storage, but when i tally up all the apps in the 'all' tab it totals approximately 40mb... I'm really stuck and it's really starting to frustrate me....
You're frustrating everyone. Do some reading bro.
Sent from my HTC One using Tapatalk
went back and factory reset my phone and even though the apps are all still there, it now says i have 1.92gb available... any idea what might be going on?
nobody is forcing you to read the thread dude...
Jrock_Xtreme said:
went back and factory reset my phone and even though the apps are all still there, it now says i have 1.92gb available... any idea what might be going on?
Click to expand...
Click to collapse
Sounds like you may have been installing the ROM incorrectly. Also one of the first steps of troubleshooting odd issues is a factory reset (Which MUST be done when installing roms of different types) Coming from TW and going to CM like you did requires FULL wipe!!
Jrock_Xtreme said:
nobody is forcing you to read the thread dude...
Click to expand...
Click to collapse
A response like that is not going to help you get too much help around here. @xcrazydx is correct. It sounds like you need to do some more ready.. especially if you are thinking of messing with partitions.
OK wow thread didn't load before I tried to answer lol. Anyway dude is a brick in the making.
Sent from my SGH-I727 using Tapatalk
i did factory wipe before and after flashing each of the roms. As i stated above, the storage glitch occurred after installing gapps and email/exchange... i only wiped cache/dalvik after installing those two. I suppose i should have factory wiped to be safe...
The reason i came asking about repartitioning and .pit files was because i had already searched and found a dev that had created custom partition tables (pit files) but they were for a different phone. I just wondered if anyone in this forum had seen and/or created them.
If not, that's cool, but i figured I'd ask. The only stupid questions are the ones you don't ask!
Hi fellow xda-members,
I recently wiped my One XL 32GB with the HBOOT Factory Reset,
didnt know that it wipes the internal storage aswell...
Needless to say that I work with the phone and the data is priceless...
I already tried to pipe the whole mmcblk0 via netcat, which worked fine.
All but the FAT 25GB partition are getting recognised via testdisk.
Did 2 dd's, so I got 2 raw-images of mmcblk0 and mmcblk0p36.
None of the recovery tools (Recuva, testdisk, @active, pc inspector recovery, etc.) did find any files.
The Partition wasnt formatted and also wasnt mounted yet, there should be no changes made from android since the wipe.
If I open the mmcblk0p36 via hex editor, its complete null.
The mmcblk0 image has random data all over the whole area,
but also mostly null (estimated 80-90% null). The internal memory was almost full,
about 22/25GB, so there are 3 options:
1.:The HBOOT Factory Reset doesnt delete just the FAT, but also nulls the whole data. (Which would be weird, because the reset took 3-5 seconds, I doubt it can null 25gigs in 5 seconds ;D)
2.:The chip has a kind of "fast-wipe" option, which makes it possible to null 25gb in 5 seconds, never seen this before, but who knows
3.:The data wasnt nulled, but dd doesnt read 1:1, which would be also weird.
Is there any app/commandline tool for android to directly check
whats on the specific part of the internal storage?
Or are there ways to access the memory directly to get
a exact image of the internal storage for recovery other than "dd if=/dev/block/mmcblk0"?
If none of the above, is there a chip-recovery expert that can recover the files with jtag/advanced hardware?
Thanks for all replys
criestr
Was the phone modified? If so, the factory reset in the bootloader doesn't just wipe the data, but it completely corrupts it, that's probably why you're getting no data show up with the recovery tools you're using.
Sent from my Evita
timmaaa said:
Was the phone modified? If so, the factory reset in the bootloader doesn't just wipe the data, but it completely corrupts it, that's probably why you're getting no data show up with the recovery tools you're using.
Sent from my Evita
Click to expand...
Click to collapse
Yes, the phone is rooted and s-off'ed,
I personally didnt change the partition alignment,
but updated the hboot from somewhat 1.09 to 2.18 a few days before.
Has the layout been changed in the past?
And, if the data was really corrupted, what to do about?
Is there any chance to recover the files?
thanks
criestr
criestr said:
Yes, the phone is rooted and s-off'ed,
I personally didnt change the partition alignment,
but updated the hboot from somewhat 1.09 to 2.18 a few days before.
Has the layout been changed in the past?
And, if the data was really corrupted, what to do about?
Is there any chance to recover the files?
thanks
criestr
Click to expand...
Click to collapse
I don't see how the partition alignment is relevant, but no I don't believe it's changed. I don't think you're going to have much luck in recovering your data, if all those recovery tools aren't yielding any positive results.
timmaaa said:
I don't see how the partition alignment is relevant, but no I don't believe it's changed. I don't think you're going to have much luck in recovering your data, if all those recovery tools aren't yielding any positive results.
Click to expand...
Click to collapse
If the partition alignment has changed, the hboot factory reset could possibly null more/less/other/the wrong ranges of memory while wiping.
I have new results:
I've checked the fresh raw dumps with a hex editor, finding out the range of mmcblk0p36, the internal sdcard only contains nulls.
Thats why every recovery tool doesnt gather any file.
I know that dd copys every bit 1:1, so I am out of luck with dd.
Does someone have experience with jtag raw data recovery?
Is there a way to gather other/deeper data with jtag?
Thanks
criestr
Hey guys, its been a long time since I've been on here asking questions, but I am completely stumped. I got an Irulu Victory 1S china phone. I achieved root, installed CWM. Problem was there was not enough storage space on main drive, as it was partitioned at 800mb for system apps and 5gigs internal SD storage. I found an app specifically for that phone manufacturer that partitioned the drive to 2.5 gigs. Flashed new Rom, Cyogen, now I am stuck in a boot loop. I can get into CWM no problem. But no matter what Rom I install, even after clearing delvik, cache, system, it just boot loops. I found from manufacturers website the original disk img files, but when using MTKtools it says disk size doesn't match file. I found a a blog that has a more detailed instructions on how to modify MBR and EBR1 using editors, but nothing on how to fix size issues. Any help is appreiated. I have win10 and Linux Mint systems if that helps any. Im assuming that there is a file or something I need to edit to get new roms to boot. I can do remote desktop sessions as well if needed. Im not computer dumb, but I know enough to get around windows and linux.
PS: I can only boot into recovery, when I ADB Shell it, it comes up as 123456789ABCDE RECOVERY as device. Cant seem to pull or push any files this way.
Update; Ok so I tried using EBR edit tool. Modified EBR to 2.5 gigs. Did a system, cache, and delvik wipe. Tried to install rom. Now it finds package, starts to open it, and then goes back to CWM main page. Tried several Roms with same results. It starts to install, but then flashes back to main recovery page. Now Im even more confused!
Hello,
Best bet is to get your partitions restored to factory partition table and then try flashing the stock firmware.
When in recovery, have you tried doing a full system and data wipe with the advanced wipe options and then flashing your ROM?
I'm not familiar with your device to give you better answers. Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help?
The experts there may be able to help.
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Michael B.N. said:
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Click to expand...
Click to collapse
The problem occurs when you use a ROM which encrypts the software or the ROM your flashing has an encrypted kernal. The only way out is to flash a ROM which doesn't encrypt. It is a known problem with TWRP and we have to wait for the TWRP team to update TWRP to handle quota allocation.
It seems the problem is solved for me. I flashed the TWRP version from this link: https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
First I tried from Odin but it didn't work. Then I installed the TWRP app from Google Play and flashed the other file, rebooted to recovery, and it seems to work. I can mount my internal storage, make a backup etc. So this is the solution for me.
I had also similar problem of internal storage 0mb and i was not be able to mount my data
so when i flash color recovery by nobody
It's gone because it's allready patch by him
I think it's issue of encrypt data so just flash this recovery from nobody post
https://forum.xda-developers.com/galaxy-s7/themes/recovery-twrps-colored-t3859323
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
i think you must try with different file mngr, that one have no ability or permission to read system files
noniboyba said:
i think you must try with different file mngr, that one have no ability or permission to read system files
Click to expand...
Click to collapse
I'll re flash later and try a different file manager. Otherwise I'll install treble or re flash stock and start over
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
same problem, have you found solution ? please help me
TWRP sometimes can't mount the storage, the storage is encrypted, but don't worry. You can still flash your files and rewrite system partion. But in order to show the Storage, you have to use a different version of TWRP. Why am I saying this is mentioned following:
I installed the latest version of twrp, It didn't ask for any password patter to decrypt my storage. So , different XDA posts made me understand that , formatting everything, factory reset will decrypt my storage. And trust me, I have done it several time, several times my brother but it didn't decrypt my storage. I couldn't backup my ROM and without backing up my ROM, I didn't take the risk of flashing new ROM. I waited. This twrp couldn't even mount my system partion. So I seeked knowledge from different person. It took a lot of effort.
Then I learned that, I should change this version of TWRP. I changed to an older version and it didn't decrypt my internal storage after formatting, but it mounted my system partion. Since, it couldn't decrypt my internal storage, I couldn't take backup of my rom and save it to internal storage. so I inserted a pendrive in my phone, and saved the backup of my rom there.
Permanent Solution
Flashing DM Verity Force Encryption Disabler will decrypt your storage instantly. But in my case, it aroused another problem, None of the security measures of my phone worked afterwards. FOD, pin, password, pattern none of them worked. I don't know the reason but I don't suggest it with my little knowledge. but almost every rom flasher use them, so I thing I have to study about them to know how they work.
second and best option: start trying older version of TWRP, the good one will be the one to ask the password the recovery in the beginning. It will decrypt your internal storage.
I was brief here, if anyone doesn't understand these things, let me know, I will explain them step by step because I know the pain of being NEWB.