I'm incredibly green when it comes to this, so please bear with me.
During the Linux screen where it asks me to Hold down the Volume Up or D Pad Button the Installer never launches when I do either action. What does happen however is, I see stuff being typed as I press the middle DPAD Button and nothing at all being typed when I press the Volume Up. Every other button is assigned characters such as ^2, ^3, ^4, etc.
No matter what button I've tried holding during that part, nothing every launches or opens.
Help would be greatly appreciated.
Thanks!
foolosophy said:
I'm incredibly green when it comes to this, so please bear with me.
During the Linux screen where it asks me to Hold down the Volume Up or D Pad Button the Installer never launches when I do either action. What does happen however is, I see stuff being typed as I press the middle DPAD Button and nothing at all being typed when I press the Volume Up. Every other button is assigned characters such as ^2, ^3, ^4, etc.
No matter what button I've tried holding during that part, nothing every launches or opens.
Help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
yeah that shows up, just hold down the d-pad center button for a osecond or two then let go then hold it down again, etc
mrono said:
yeah that shows up, just hold down the d-pad center button for a osecond or two then let go then hold it down again, etc
Click to expand...
Click to collapse
I've tried it, nothing happens. It just types another ^@ symbol, no matter how long I hold, or how many times I stop holding and rehold.
foolosophy said:
I've tried it, nothing happens. It just types another ^@ symbol, no matter how long I hold, or how many times I stop holding and rehold.
Click to expand...
Click to collapse
Have you tried reflashing? Maybe try different versions of the kernel?
foolosophy said:
I've tried it, nothing happens. It just types another ^@ symbol, no matter how long I hold, or how many times I stop holding and rehold.
Click to expand...
Click to collapse
Try to get the latest package from myn. it should work ok.
vogue android should be discussed in the vogue android forum http://forum.xda-developers.com/forumdisplay.php?f=588
egzthunder1 said:
Try to get the latest package from myn. it should work ok.
Click to expand...
Click to collapse
Tried, same issue.
Any other suggestions?
When you press the d pad to run haret keep it pressed that's how I get it to work and do you have all the needed files to boot android
sak211l said:
When you press the d pad to run haret keep it pressed that's how I get it to work and do you have all the needed files to boot android
Click to expand...
Click to collapse
I did this but I was not aware that it wipes out windows mobile 6.5-I thought this was a dual boot install
narottam said:
I did this but I was not aware that it wipes out windows mobile 6.5-I thought this was a dual boot install
Click to expand...
Click to collapse
It doesn't unless you are installing in NAND. If you run from SD card, it will tell you that it is about to wipe all your data, but that only relates to Android files present in your card.
Thread Moved to Vogue Android Section.
Same problem
I am having the same problem. Used different kernels, tried to install from nand and SD card. Used 2 different SD cards and the same problem, the installer fails to load.
Mentioned this in Myms thread but no reponses
Heres my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7653 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (11080) not free
Fix? yes
5 files, 3001800 free (1948089 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argumen
Did have this working, but went back and did the "Verizon GPS fix". After that the installer would never load.
Thanks
gorm said:
I am having the same problem. Used different kernels, tried to install from nand and SD card. Used 2 different SD cards and the same problem, the installer fails to load.
Mentioned this in Myms thread but no reponses
Heres my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7653 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (11080) not free
Fix? yes
5 files, 3001800 free (1948089 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argumen
Did have this working, but went back and did the "Verizon GPS fix". After that the installer would never load.
Thanks
Click to expand...
Click to collapse
Try to hard reset your WM and then use HaRet.
Thanks but I tried that this morning.
After running the Android OS on this phone, I just dont want to have to go back to Win MO
gorm said:
I am having the same problem. Used different kernels, tried to install from nand and SD card. Used 2 different SD cards and the same problem, the installer fails to load.
Mentioned this in Myms thread but no reponses
Heres my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7653 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (11080) not free
Fix? yes
5 files, 3001800 free (1948089 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argumen
Did have this working, but went back and did the "Verizon GPS fix". After that the installer would never load.
Thanks
Click to expand...
Click to collapse
Ok, so you CANNOT get into the installer? Do you ultimately want to use sd or nand? After doing the verizon GPS fix, did you reflash an android nbh?
would rather use nand. I have tried many different android nbhs from back in FEB . to the most recent dated kernels.
gorm said:
would rather use nand. I have tried many different android nbhs from back in FEB . to the most recent dated kernels.
Click to expand...
Click to collapse
Ok, so after running the verizon gps fix you did flash an nbh (correct?) and now when the phone boots you can't get into the installer by holding a button or the screen?
mrkite38 said:
Ok, so after running the verizon gps fix you did flash an nbh (correct?) and now when the phone boots you can't get into the installer by holding a button or the screen?
Click to expand...
Click to collapse
Yes that is correct.
gorm said:
Yes that is correct.
Click to expand...
Click to collapse
Are you seeing the 'Press to enter installer' message go by?
mrkite38 said:
Are you seeing the 'Press to enter installer' message go by?
Click to expand...
Click to collapse
Yes I am seeing the installer message, just nothing happens when I press the d pad or any other button. I have tried them all.
Just as foolosophy posted in post #3
TIA
Ok, so my basic problem is my Verizon Tablet suddenly wouldn't get past the samsung screen on bootup. This happened suddenly without me changing anything at all. Just turned it on one day and BAM.
First guess was to boot into recovery and do a wipe data/factory reset.
When I do this it just goes to the first line "formatting /data..." and hangs for a long time. Eventually it prints this out
Code:
--Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard.android_secure!
Skipping format...
Data wipe complete.
I currently do NOT have my SD card inserted as I didn't want to to hurt it during all my messing about fixing this. FYI
I tried giving it its kernel again, and then tried other kernels i'v found around the forum with no change.
I used the Heimdall One-Click found here: http://forum.xda-developers.com/showthread.php?t=1323527 with still no change. But now that I'm running a stock kernel I get this error message as soon as I get into recovery
Code:
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
When I try a wipe data/factory reset I get this error
Code:
update application, please wait
E:Can't mount /dev/block/mmcblk0p2
(Invalid argument)
E:install_application_for_customer:Can't mount DATA:
your storage not prepared yet, please use UI menu for format a
nd reboot actions.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
After doing a bunch of searching I found this page:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partition-on-internal-storage
Post number 7 is where the good info is. I have to upgrade my kernel to one that is rooted (like clockworkmod 5.0.2.7) so I can push the files to the correct spots. From the shell using ADB I type
Code:
parted /dev/block/mmcblk0
If I type print I get this:
Code:
Number Start End Size Type File system Flags
1 32.8kB 220MB 220MB primary ext4
2 220MB 1539MB 1319MB primary ext4
3 1539MB 1959MB 419MB primary fat16
when I type mkfs ext2 I get this error message
Error: File System was not cleanly unmounted! you should run e2fsck.
When I try to run e2fsck /dev/block/mmcblk0 It says this
The superblock could not be read or does not describe a correct ext filesystem.
So Im thinking these programs cannot edit a ext4 filesystem. Since the plan is to format them anyway, I'll delete and recreate them. I did see this on a page somewhere but I cant find that one for the life of me... sorry.
parted /dev/block/mmcblk0
rm 1
rm 2
None of that gives any error messages, but when I print it still shows the same file system, both partitions I just deleted are still there.
So maybe i'm just using parted wrong or it is bugging out? So i try fdisk
Code:
fdisk /dev/block/mmcblk0
p
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 26880 215008 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26881 187904 1288192 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
Partition 3 does not end on cylinder boundary
d (to delete partition)
Partition Number (1-4): 1
d
Partition Number (1-4): 2
p (to print partition table)
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
w (to write and exit)
So that seemed to work right, I I deleted partition 1 and 2 then looked at the table and they are gone and I wrote it. Now I go back into it and BAH, nothing has changed!
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 26880 215008 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26881 187904 1288192 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 187905 239104 409600 83 Linux
Partition 3 does not end on cylinder boundary
I'v used many diffrent Kernels and tried a few different roms (not like its loading that far anyway)
The best I'v gotten it to do is when using Heimdall One-Click it will go past the samsung screen to the Verizon screen. I'v waited at that screen for a very long time with no change...
At this point, i'm stumped. I have no idea where to go next or if I'm even on the right track.
Any help would be greatly appreciated.
Thanks!
I was getting this exact same error on my AT&T Tab. I fixed it by flashing JJ7 from samfirmware.com. Here's what I did:
http://forum.xda-developers.com/showthread.php?t=1388470
check my post there. Obviously you'll have to use a firmware compatible with your VZW Tab, but it might work for ya.
Good Luck.
Hello I'm trying to get complete Linux to work with our Razer but when I try and boot one of the images I get checking loop device... FOUND
mount: mounting /storage on /data/local/mnt/external_sd failed: Invalid argument
No user defined mount points
net.ipv4.ip_forward = 1
chroot: can't execute '/root/init.sh': No such file or directory
Shutting down Linux ARM
umount: can't umount /data/local/mnt/external_sd: Invalid argument
I need help getting this to work tryed editing the bootscript.sh can't get it to work
Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.
白い熊 said:
Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.
Click to expand...
Click to collapse
cant you simply wipe the affected partitions(except data of course)? then flash a rom?
have you tried;
mount /sys/block/sda25 /mydata
or
mount /dev/block/sda25 /mydata
or
adb
mount -o rw /dev/block/sda25/data /mydata
in both cases /mydata is just the mount point so I believe it can simply be called what ever you want including just /data
have you read:
https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
edit:
by any chance when you first flashed twrp, did you forget to format data?
if yes then flash back stock AP file(original phone's firmware) in Odin AP slot only and you should be good to go.( you shouldn't loose any files in internal storage)