Related
I do the flash without further study, and I accidentally flash my samsung fascinate with I9000 Pit 512, and now I can't get back to stock verizon. Can anyone please help me?
thanks.
kenpachi069 said:
I do the flash without further study, and I accidentally flash my samsung fascinate with I9000 Pit 512, and now I can't get back to stock verizon. Can anyone please help me?
thanks.
Click to expand...
Click to collapse
I did something similar.. don't worry too much.. yet..
Let me find my post on this.. basically, I had to flash the US cellular kernel, then it would allow the stock fascinate kernel to take.
So flash US cellular..
then flash stock Fascinate
Here
http://forum.xda-developers.com/showpost.php?p=8195563&postcount=43
thank you
Thank you for a quick reply. I will try and let you know..
namebrandon said:
I did something similar.. don't worry too much.. yet..
Let me find my post on this.. basically, I had to flash the US cellular kernel, then it would allow the stock fascinate kernel to take.
So flash US cellular..
then flash stock Fascinate
Here
Click to expand...
Click to collapse
I tried, and it still doesn't work. I think the problem is not the kernel. The problem is the PIT file that I also flashed. I need to map to the right place, I can't find i500 PIT file anywhere. I hope someone can direct me. thanks.
kenpachi069 said:
I tried, and it still doesn't work. I think the problem is not the kernel. The problem is the PIT file that I also flashed. I need to map to the right place, I can't find i500 PIT file anywhere. I hope someone can direct me. thanks.
Click to expand...
Click to collapse
I've got it at home, but not here. I got it from angel (fallingup) originally. PM him.
namebrandon said:
I've got it at home, but not here. I got it from angel (fallingup) originally. PM him.
Click to expand...
Click to collapse
If you get home can you upload it for me, please?
Thanks.
Gotta love dropbox. extract from zip.
namebrandon said:
Gotta love dropbox. extract from zip.
Click to expand...
Click to collapse
Nice, thank you so much. Now i just have to find the right file to flash it back. Where do i get the file for pda, phone, and csc?
Sorry, I am really noob to android. Once again, thank you for all the help.
kenpachi069 said:
Nice, thank you so much. Now i just have to find the right file to flash it back. Where do i get the file for pda, phone, and csc?
Sorry, I am really noob to android. Once again, thank you for all the help.
Click to expand...
Click to collapse
You only use PDA.. And rarely would you ever use the PIT file.
You can find the stock odin files here, in the first post.
http://forum.xda-developers.com/showthread.php?t=782204
namebrandon said:
You only use PDA.. And rarely would you ever use the PIT file.
You can find the stock odin files here, in the first post.
Click to expand...
Click to collapse
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
kenpachi069 said:
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
Click to expand...
Click to collapse
What does..? I don't know what "it" is man.. Is that during recovery?
Regardless, if you're getting that output from the phone, we're heading in the right direction.
Well after I do the system restore, it just reboot and that's what it say.
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
It won't start up.
kenpachi069 said:
Well after I do the system restore, it just reboot and that's what it say.
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
It won't start up.
Click to expand...
Click to collapse
Ok.. You need to start over.. using the files from the post I linked to..
Start Odin, and flash the /system file. You use the PDA box. You do not put anything in PIT.
Then do the same thing, but use the stock kernel file.
Then do the same thing, and use the stock recovery file.
namebrandon said:
Ok.. You need to start over.. using the files from the post I linked to..
Start Odin, and flash the /system file. You use the PDA box. You do not put anything in PIT.
Then do the same thing, but use the stock kernel file.
Then do the same thing, and use the stock recovery file.
Click to expand...
Click to collapse
There is a PIT file in that thread now. Use it if you flashed another phone's pit file.
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
I am stuck at this after doing one click restore odin3 for captivate on galaxy s i500.
i can get to download mode, using homemade jig.
please someone help me when i flash my phone to atleast normal mode. please
kenpachi069 said:
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
Click to expand...
Click to collapse
This means ur phones file systems those 2: stl11 is your /system/ and mmcblk0p1 is your /data/ and if it cant read it then that means you must have had voodoo 5 enabled and it converted all of ur file system to ext4
Sent from my SCH-I500 using XDA App
atinder said:
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
I am stuck at this after doing one click restore odin3 for captivate on galaxy s i500.
i can get to download mode, using homemade jig.
please someone help me when i flash my phone to atleast normal mode. please
Click to expand...
Click to collapse
I have several questions...
1) Why does getting into download mode require a homemade jig?
2) What were you running before you tried to restore back to stock?
....oh what was that third one....OH YEA
3) Why on gods green earth would you use the one click restore for the captivate on the fascinate!? If you got it from here...you'll notice that in all caps in the title it says "CAPTIVATE ONLY". le sigh.
This is the thread with the files you need: http://forum.xda-developers.com/showthread.php?t=782204
I'm not sure if the one click restore also writes over your modem...but if it did you need to go into irc (irc.freenode.net #samsung-facinate) and ask someone for it.
In addition, if you were running voodoo before doing this you'll need someone more acquainted with these sort of facepalm dilemmas. These people can also be found in irc.
Advice: Read Read Read....and don't think about or mention taking your phone in to verizon. The irc gods will smite you.
If you flashed another galaxy S's ANYTHING, you now have a brick.
Now go ahead and pat yourself on the back. You've earned it.
Also, this thread is totally in the wrong section. Just sayin'.
Sent from my SCH-I500 using XDA App
times_infinity said:
If you flashed another galaxy S's ANYTHING, you now have a brick.
Now go ahead and pat yourself on the back. You've earned it.
Also, this thread is totally in the wrong section. Just sayin'.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
False..
It's a stupid move, but far from a brick.
atinder said:
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
Click to expand...
Click to collapse
You need to follow this http://forum.xda-developers.com/showthread.php?t=804784
Redwing said:
I have several questions...
In addition, if you were running voodoo before doing this you'll need someone more acquainted with these sort of facepalm dilemmas. These people can also be found in irc.
Advice: Read Read Read....and don't think about or mention taking your phone in to verizon. The irc gods will smite you.
Click to expand...
Click to collapse
Completely agree.
supercurio has reported:
SpeedMod based (Doc's ROM and others) and every other Universal Lagfix corrupt badly /system
It means that as long as they don't restore a /system with Odin, they're stuck on kernels using broken mount options.
If you want to verify, try to boot a stock Samsung kernel. Depends on how much it is corrupt it will boot, or not, or with unexpected errors
Want proof?
http://bit.ly/bq2oXg
Highlighted line is using wrong and corruption mount points
lack of check=no which causes corruption. Every Samsung mount uses check=no
Second Issue:
Even with NO RFS Config selected... RFS is still used in /system mounts... means phone are slowly Dying of corruption..
please fix linky - I want to know more about this:
That page doesn't exist!
Click to expand...
Click to collapse
thanks !
zacharias.maladroit said:
please fix linky - I want to know more about this:
thanks !
Click to expand...
Click to collapse
Fixed XD Sorry for that
Not 100% sure on this, since I have not used or looked at sztupy's lagfix very much, but that line you are pointing out is not a problem.
If /system is EXT4, then calling mount -t rfs on it will simply return an error message, and not mount it. It will do exactly nothing.
The following line would then mount it correctly.
Basically, this seems to be totally false. More evidence please.
EDIT: Okay, OP was updated with better information. Lack of check=no means that the FAT32 check *may* be running on the /system, which would cause corruption.
Probably a good idea to confirm if the filesystem check is actually happening though!
In case that supercurio is right (I hope he’s not for obvious reasons), I guess that it wont affect to users that are running harcore kernel without any lagfix applied, right?
RyanZA said:
If /system is EXT4, then calling mount -t rfs on it will simply return an error message, and not mount it. It will do exactly nothing.
The following line would then mount it correctly.
Click to expand...
Click to collapse
That is correct, however /system is not EXT4, but RFS.
good catch.
but im sure sztupy can fix this with a small patch, although i agree the priority should be flagged 'critical'...
as always, good work supercurio
NetCopAD said:
That is correct, however /system is not EXT4, but RFS.
Click to expand...
Click to collapse
Thanks, I thought this was referring to a problem when /system is converted, rather than when it isn't. Which means that if you are running sztupy's kernel with one of the settings that convert /system then it should be fine.
In case that supercurio is right (I hope he’s not for obvious reasons), I guess that it wont affect to users that are running harcore kernel without any lagfix applied, right?
Click to expand...
Click to collapse
It would actually affect you in this case, as the problem occurs when the lagfix is NOT applied, rather than when it is applied!
If it even is a problem, and the fat32 check runs rather than the system trying to do fsck.rfs and failing.
RyanZA said:
Thanks, I thought this was referring to a problem when /system is converted, rather than when it isn't. Which means that if you are running sztupy's kernel with one of the settings that convert /system then it should be fine.
It would actually affect you in this case, as the problem occurs when the lagfix is NOT applied, rather than when it is applied!
If it even is a problem, and the fat32 check runs rather than the system trying to do fsck.rfs and failing.
Click to expand...
Click to collapse
Maybe I am wrong but there is no settings in sztupy's kernel which convert /system
Lagfix only convert /data, /cache and /dbdata
Mopral said:
Maybe I am wrong but there is no settings in sztupy's kernel which convert /system
Lagfix only convert /data, /cache and /dbdata
Click to expand...
Click to collapse
Yeah i just looking further system is still mounted as
/sbin/busybox mount -t rfs /dev/block/stl9 /system - Possible corruption happens here without check=no
RyanZA said:
Thanks, I thought this was referring to a problem when /system is converted, rather than when it isn't. Which means that if you are running sztupy's kernel with one of the settings that convert /system then it should be fine.
It would actually affect you in this case, as the problem occurs when the lagfix is NOT applied, rather than when it is applied!
If it even is a problem, and the fat32 check runs rather than the system trying to do fsck.rfs and failing.
Click to expand...
Click to collapse
Yes this would affect the speedmod kernel as well, if it indeed is a problem. ULFK does not change /system in any lagfix scheme. So, its always mounted as rfs, apparently "wrongly".
I am testing an updated speedmod (shall we say, K9-pre) with the changed mount option. At the very least it should do no harm. And trying to get in touch with curio but over at IRC they say he's probably sleeping now after a coding binge!
Hmm and I found a minor 'bug' in the post-init.sh that was not properly setting /system to read-only after its done.... mainly because the logfile is being written to /system!
Method to test if this is a problem:
Replace your fsck_msdos (this is the only fat32 fsck in the filesystem) with a script file. Inside the script put the following:
Code:
echo "$?" > /somewhere
Then reboot your phone a lot of times. If the check is being called, then you will now get a log message instead of the check happening.
Will also affect checking of /sdcard though.
As far as I know though, fsck_msdos is only ever called by vold, and therefore check=no in /system may not have any effect, and this could be a false alarm. Anyway as hardcore says, can't hurt to fix it!
EDIT: Just wanted to add that running fsck_msdos even once on my /system (using the awesome pre-init scripts from z4mod!) made my phone immediately unbootable (damnit!). Not a big sample size, but I believe that if this was really a problem, we would be seeing many many reports of the sztupy kernel breaking devices! Since we don't have these reports, I'm gonna put this myth down as 'likely to be busted soon!'
RyanZA said:
Method to test if this is a problem:
Replace your fsck_msdos (this is the only fat32 fsck in the filesystem) with a script file. Inside the script put the following:
Code:
echo "$?" > /somewhere
Then reboot your phone a lot of times. If the check is being called, then you will now get a log message instead of the check happening.
Will also affect checking of /sdcard though.
As far as I know though, fsck_msdos is only ever called by vold, and therefore check=no in /system may not have any effect, and this could be a false alarm. Anyway as hardcore says, can't hurt to fix it!
Click to expand...
Click to collapse
Well the intention of this post is to show the issue for it to be fixed So let hope it does not do too much damage :S
deathst said:
Well the intention of this post is to show the issue for it to be fixed So let hope it does not do too much damage :S
Click to expand...
Click to collapse
Looks like this may have been a bit too sensationalist!
More checking, less guessing is always good! (And I could learn a lot from that motto myself!! )
RyanZA said:
Looks like this may have been a bit too sensationalist!
More checking, less guessing is always good! (And I could learn a lot from that motto myself!! )
Click to expand...
Click to collapse
Well we could check it by running it on RFS and reboot alot of time and then flashing a original Kernel
RyanZA said:
Looks like this may have been a bit too sensationalist!
More checking, less guessing is always good! (And I could learn a lot from that motto myself!! )
Click to expand...
Click to collapse
yeah when i saw that post my balls shrank.. thinking that by precious phone may be 'slowly dying of corruption'
not like there is a repair file system tool to use
Code:
/dev/block/stl9 /system rfs ro,noatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
K8, u had a short life... looks like its time for K9
Important thing to note is that this is the way stock kernels mount /system: read-only, and we see the option log_off too.
The thing I noticed this way is that if u do a mount -o remount,rw /system and modify stuff... it may corrupt /system. All modifications to /system should then ideally be done via CWM or update.zip only.
deathst said:
Well we could check it by running it on RFS and reboot alot of time and then flashing a original Kernel
Click to expand...
Click to collapse
Why would flashing an original kernel make a difference? Original kernel will mount /system in exactly the same way, so any corruption in /system would be seen on both the original kernel and on the sztupy kernel before the reflash.
Reflash or not has nothing to do with it.
Only method would be to reboot (or remount) enough times to hit the unclean filesystem check parameter (which rfs might not even have?), or wait long enough for the unclean check time to elapse. Not really sure how you would check what this parameter is - maybe tune2fs could be used? RFS is a bit of a black box!
RyanZA said:
Why would flashing an original kernel make a difference? Original kernel will mount /system in exactly the same way, so any corruption in /system would be seen on both the original kernel and on the sztupy kernel before the reflash.
Reflash or not has nothing to do with it.
Only method would be to reboot (or remount) enough times to hit the unclean filesystem check parameter (which rfs might not even have?), or wait long enough for the unclean check time to elapse. Not really sure how you would check what this parameter is - maybe tune2fs could be used? RFS is a bit of a black box!
Click to expand...
Click to collapse
It may mount correctly with Original Kernel..If it does quite a damage to the /system the phone might report errors even it is will not be able to boot.
deathst said:
It may mount correctly with Original Kernel..If it does quite a damage to the /system the phone might report errors even it is will not be able to boot.
Click to expand...
Click to collapse
No, that doesn't make sense. The difference between stock and sztupy is that sztupy's mount is telling the system to try and check the drive. If /system works fine in the sztupy kernel, it will still work fine in the stock kernel, because the only difference is that the stock kernel DOESN'T check. Well, testing so far seems to be showing that neither check, and the check option does nothing at all.
I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
**UPDATE** 06/18/2012
by following this ( http://forum.xda-developers.com/showthread.php?t=919353 ) guide, i am able to get some result with sudo:
Code:
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
Then I try entering the quoted commands and even attempt to edit them, but the result sucks:
Code:
[email protected]:~$ dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: opening `/sdcard/boot.img': No such file or directory
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb shell
~ # dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/sdcard/boot.img': No such file or directory
~ # dd if=/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/boot.img': No such file or directory
~ # dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
dd: can't open '/sdcard/system.img': No such file or directory
the reason for this is that I can't mount the sdcard. if i could mount the sdcard, then this would be an easy fix and i never would have posted in the first place. using CWM 3.2.0.1 in place of nookie froyo since EVERY link for nookie froyo i have found has been a dead link or the instructions require mounting the sdcard which is the problem i am having. Also, CWM 3.2.0.1 and TWRP 3.2.0.1 or older are the ONLY things that actually allows the NC to turn on.
XSmoky said:
I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
Click to expand...
Click to collapse
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
leapinlar said:
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
Click to expand...
Click to collapse
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
XSmoky said:
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
Click to expand...
Click to collapse
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
leapinlar said:
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
Click to expand...
Click to collapse
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
XSmoky said:
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
Click to expand...
Click to collapse
No error messages and being able to read in your PC does not necessarily mean it will boot from it.
But like I said, I'm not sure it would have helped you anyway. Did you look at this thread?
http://forum.xda-developers.com/showthread.php?p=25433167
Your problem is that your partitions have gotten corrupted.... you will need to dd some img's back to the nook... I have all of them available... but for /dev/block/mmcblk0p2 and 0p3 you will need to do some editing... since they are device specific.
If you're lucky... /dev/block/mmcblk0p3 is still "normal" and the device can recover 0p2 from the rombackup.zip on there... if not... editing is in your future.
Anyway... if you need the img files... I can make them available... have helped a few out with this problem.
Thanks guys, I'm gonna dual boot linux and get to work on the harder to do things now, but with my kids running around it'll take me some time to do.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
lufc said:
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Click to expand...
Click to collapse
Thought i was in the right place given other similar issues posted in same area, thanks for putting me in the right place.
****Moderator please delete this extra post****
Ive unlocked it and followed the proper steps to root it but when im in Clockworks mod or TWRP, I get the same "cannot mount" errors like unable to mount /data etc etc.
Thinking i did something wrong, i looked for an alternative and found wugs Nexus Root Toolkit 2.0.5
Everything runs smoothly, even did a successful factory flash to 5.1.1 and retried rooting.
Same errors, unable to mount. Im not sure whats causing these errors but would it have something to do with "secure boot enabled" ?
Ive been googling this since yesterday and I cant find a concrete answer as too why TWRP cannot mount or find anything.
Nexus 7 2013 LMY47V
Some errors:
E: Unable to find partition size for '/boot' and '/recovery' and '/misc'
E: Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '.data' is not present!
E: unable to recreate /data/media folder.
E: unable to find partition size for '/sbl1/
E: unable to mount '/system' and '/data' and '/cache'
Nothing? Am I missing something completely obvious? Sorry if I am, ive only ever rooted a kindle fire hd once a few years ago.
I guess ill be using no root firewall then? Funny thing I always though the adblock app needed root to work but its working without it.
Shame I cant remove hardware programs like "google +"
cerbyd said:
Ive unlocked it and followed the proper steps to root it but when im in Clockworks mod or TWRP, I get the same "cannot mount" errors like unable to mount /data etc etc.
Thinking i did something wrong, i looked for an alternative and found wugs Nexus Root Toolkit 2.0.5
Everything runs smoothly, even did a successful factory flash to 5.1.1 and retried rooting.
Same errors, unable to mount. Im not sure whats causing these errors but would it have something to do with "secure boot enabled" ?
Ive been googling this since yesterday and I cant find a concrete answer as too why TWRP cannot mount or find anything.
Nexus 7 2013 LMY47V
Some errors:
E: Unable to find partition size for '/boot' and '/recovery' and '/misc'
E: Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '.data' is not present!
E: unable to recreate /data/media folder.
E: unable to find partition size for '/sbl1/
E: unable to mount '/system' and '/data' and '/cache'
Click to expand...
Click to collapse
Wow i have the same **** with mine same version and same device... you find a solution
I was having the same issue and after a few hours of searching, I found this post: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
It seems like there's a new version out that doesn't work quite as easily as just flashing the latest TWRP version.
To be quick, I have a very specific error in all TWRP versions on LS997 that won't let the system stay mounted while flashing roms, "Failed to mount '/system' (invalid argument)".
I believe I found a fix for it in a dead reddit thread, but I can't understand how to do it on an LG v20.
Help is much appreciated.
It reads
"for anybody that stumbles upon this thread: I got it working by using a parted binary and mkfs.ext4 binary.
I removed the partition and added it again with parted, don't forget to name it correctly. And then I reformatted with mkfs.ext4. Those three links might help:
https://en.miui.com/thread-340966-1-1.html
https://android.stackexchange.com/q...in-terminal-emulator-on-my-android-smartphone
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171"
The thread.
https://www.reddit.com/r/LineageOS/comments/aozjvf/twrp_can_not_mount_system_with_invalid_argument/
strapdad said:
To be quick, I have a very specific error in all TWRP versions on LS997 that won't let the system stay mounted while flashing roms, "Failed to mount '/system' (invalid argument)".
I believe I found a fix for it in a dead reddit thread, but I can't understand how to do it on an LG v20.
Help is much appreciated.
It reads
"for anybody that stumbles upon this thread: I got it working by using a parted binary and mkfs.ext4 binary.
I removed the partition and added it again with parted, don't forget to name it correctly. And then I reformatted with mkfs.ext4. Those three links might help:
https://en.miui.com/thread-340966-1-1.html
https://android.stackexchange.com/q...in-terminal-emulator-on-my-android-smartphone
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171"
The thread.
https://www.reddit.com/r/LineageOS/comments/aozjvf/twrp_can_not_mount_system_with_invalid_argument/
Click to expand...
Click to collapse
I’m also looking at the thread, and the miui link is stale because miui cleaned their forum.
I tried erase data (entire partition). I tried wiping system data cache, no matter what I did it was error 7 or unable to mount system.
I’m suspecting it might be which kdz I used for the downgrade but honestly it can’t be the case because I did this before 2 months ago and it was ok, now I can’t do anything.