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.
Related
I am cross posting this as its a New firmware.
Original thread http://forum.xda-developers.com/showthread.php?t=802771
It is firmware OMJL6
I did flash this to my SC-02B and it does work, I flashed via Hiemdall and Odin, both work, the rom is sharp, and felt rather quick without lagfix...
I will warn you... DO NOT FLASH A PIT FILE AND RE PARTITION... All Pit files I have found have not worked... I have found a "SC-02B" Pit file, it gets much farther than the others, as in it does not fail, but fails once it gets to the recovery,
Code:
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!..
-- movi_checking done!...
update media, please wait
<now in red font>
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
<yellow>
your storage not prepared yet. please us UI me nu for format and reboot actions.
<red>
copy default media content failed.
I have not been able to find an OMJJ1 rom for the pit file i found, and i have been unable to find a pit file that works with OMJL6...
Soooo.... Its back to google... or if anyone has any ideas...
I will also make a note that OMJL6 has kernel included so you really don't need the stock one.... but it also does work if you just want to use it instead...
Playing with OMJL6 - z4root does not work... Super One Click however does... I read that z4mod does work... but I could not get it to work... which led me to flashing more aventuriously and flashing a pit that then led to the point I am at now... which is - at a loss for correct files -
No idea if this will help anyone, but here's the log file from my update that was applied today. Maybe there's a clue in there somewhere...?
interesting... so recovery takes commands from /cache/recovery/command
thanks for posting... I checked system and am downloading ver 1.41.xxxx something... I'll know more when its done... (here in MI)
thor2002ro said:
interesting... so recovery takes commands from /cache/recovery/command
Click to expand...
Click to collapse
Perhaps you guys could set up commands and try out some things there?
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.
What is the vendor section that appears when you want to do an advanced wipe? And why does it come out on some mobiles and not on others?
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
NOTE: I'm not a developer or something even near to that. I'm a newbie and will be, seems so. All information provided here is copied and compiled from different internet sources like this and many others. This information is according to best of...
forum.xda-developers.com
So if in twrp it says that it is impossible to mount vendor (invalid argument) is it something bad or does it not matter?
The_severo said:
So if in twrp it says that it is impossible to mount vendor (invalid argument) is it something bad or does it not matter?
Click to expand...
Click to collapse
it doesn't matter