Problems trying to install Android on HTC Vogue - Touch CDMA Android Development

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

Related

Missing files on sd card

hey guys, when i try and update my recovery through terminal emulator I get an error
after the line
"mount -a"
i get:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
mount: mounting /system/modules/modules.sqf on /system/modules failed: No such file or directory
mount: mounting /system/xbin/xbin.sqf on /system/xbin failed: No such file or directory
What is wrong here? it seems as if my sd card is missing files?! Can someone give me the files i am missing or would an sd card reformat fix it?
asb123 said:
hey guys, when i try and update my recovery through terminal emulator I get an error
after the link
"mount -a"
i get:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
mount: mounting /system/modules/modules.sqf on /system/modules failed: No such file or directory
mount: mounting /system/xbin/xbin.sqf on /system/xbin failed: No such file or directory
What is wrong here? it seems as if my sd card is missing files?! Can someone give me the files i am missing or would an sd card reformat fix it?
Click to expand...
Click to collapse
The first error means you don't have an ext2/3/4 partition and you should be fine
The second and third are common errors and don't really mean anything
Just continue flashing the recovery
alright cool, i have now got the new amon recovery!

factory.zip to mmcblk0p3

I am pretty sure my factory.zip is corrupt or nonexistant from my mmcblk0p3. How do i move the factory.zip file over there from this thread http://forum.xda-developers.com/showthread.php?t=919353
Thanks
I just did this last night. First I booted into clockwork recovery and hooked up the nook to my computer and started up adb. I tried doing this when it was booted normally but I could not mount mmcblk0p3. Anyways once you are in recovery mode go to where adb is installed. Then these were the commands I did
Code:
adb shell mount /dev/block/mmcblk0p3 /emmc
adb pull /emmc/factory.zip factory-1.0.0.zip
adb push factory.zip /emmc/
The second line is me backing up my old 1.0.0 factory zip, just in case things went bad. Then I did the 8 failed boot reset and then reset /data
Thank You! I had something like that except i was missing emmc in the first line and i couldn't figure out why i couldnt mount mmcblk0p3. I want to make a how to once i reach 10 posts on this.
Hate to bring back an old thread, but, no matter how I have tried, I cannot mount /dev/block/mmcblk0p3... I always get invalid argument error... any help is appreciated.
>adb shell mount /dev/block/mmcblk0p3 /emmc
mount: mounting /dev/block/mmcblk0p3 on /emmc failed: Invalid argument
I have yet to be able to mount mmcblk0p3 to copy factory.zip to it.... hoping this would fix my install failed error on the 8 failed boot install.
NM.... fixed it... had to mke2fs /dev/block/mmcblk0p3 before I could mount it... got it fixed... the 8 failed boots works as it should again.

complete linux errors ???

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

Phone won't accept decryption (FDE) password anymore.

My device: HTC One M7 Android 4.2.2, S-ON, Root, CWM recovery (years old version)
My ultimate goal was: Get xposed framework. Install via app failed after rebooting due to S-ON, so I wanted to install through recovery. (this is irrelevant to the issue IMO)
What I tried to get there: Decrypting my /data partition in adb (because CWM doesn't support it)
What I found: https : // forumDOTfairphoneDOTcom/t/how-to-mount-encrypted-data-in-recovery/25724
Everything(!) I actually did: (commands after $ means executed on host machine (ubuntu), prefixed by ~ # means run on phone in adb shell)
$ adb shell
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw "<wrong password>"
200 0 1
~ # mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: no such file or directory
(( a couple commands like ls and cat to find out what my /data partition should be ))
(( ended up finding out in fstab that it's mmcblk0p37 ))
~ # mount /dev/block/mmcblk0p27 ((accidentally wrong one))
mount: mounting /dev/block/mmcblk0p27 on /data failed: Invalid argument
~ # mount /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
(( notice i entered wrong password ))
~ # vdc cryptfs checkpw "<right password>"
200 0 2
~ # mount /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
(( a couple more tried of the previous two commands for no legit reason ))
~ # mount -o rw,remount /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
(( exit adb shell ))
(( execute $ adb remount )) (( as google suggested (on host machine, not in adb shell obv) ))
$ adb shell
~ # mount -t ext2 /dev/block/mmcblk0p37 (( accidentally wrong fstype ))
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
~ # mount -t ext4 /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
~ # mount -t ext4 /dev/block/mmcblk0p27 (( why not? ))
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
~ # exit (( i got frustrated ))
Before I did all this the phone was working normally (after install xposed via app (which gave me xposed version 3x because I had that one previously installed via receovery. But I wanted the newest (5x) so I went all that way)). After I did all these steps - which to me are readonly things which shouldn't brick anything - I got frustrated and wanted to give up, so I rebooted. Now everytime I enter the - 100% correct - password, it tells me to "try again" (guessing it means wrong password? idk).
The whole xposed stuff is irrelevant in my opinion, because after I've installed it using the xposed installer (APK) I rebooted twice and decryption worked fine both times.
What the hell have I done (I'd say I'm a linux expert and I honestly don't see how I could've possible broken anything by what I did) and how can I fix it?
UPDATE: I got myself the cryptheader from the "extra" partition using the read_emmc vulnerability. That way I got the encrypted key and salt. (cryptheader)
I then used this and a modified bruteforce script to check if my right password is still right. Result: It doesn't seem so.
My password contained special characters and was 15 chars long, bruteforce is not an option.
Is there anyway what I did could've changed the password? If so, can I reproduce and get the new key somehow? The cryptheader is not corrupted and still intact. The /data partition (encrypted) is not corrupted and still intact. (I assume this because the encrypted partition's hexdump starts with "This is an encrypted partition", which is a HTC easter egg.)
htcuser311 said:
UPDATE: I got myself the cryptheader from the "extra" partition using the read_emmc vulnerability. That way I got the encrypted key and salt. (cryptheader)
I then used this and a modified bruteforce script to check if my right password is still right. Result: It doesn't seem so.
My password contained special characters and was 15 chars long, bruteforce is not an option.
Is there anyway what I did could've changed the password? If so, can I reproduce and get the new key somehow? The cryptheader is not corrupted and still intact. The /data partition (encrypted) is not corrupted and still intact. (I assume this because the encrypted partition's hexdump starts with "This is an encrypted partition", which is a HTC easter egg.)
Click to expand...
Click to collapse
I'm far from being a linux expert but the simplest would be to factory reset using htc's recovery to remove /data encryption and start from scratch (unless you have some really important data that must be saved from your /data partition)
alray said:
I'm far from being a linux expert but the simplest would be to factory reset using htc's recovery to remove /data encryption and start from scratch (unless you have some really important data that must be saved from your /data partition)
Click to expand...
Click to collapse
I have decided to give up on trying and did a "factory reset" (formatted /data and /data/sdcard through CWM, rebooted, set up device for first use, formatted /data again through CWM to result in clean system).
Fun-fact: Before I did what bricked the system I actually made a backup. The device (µSD-Card) decided to go corrupted filesystem though. I managed to recover most of the files but the /system partition backup (which might have saved me) remained corrupted. I was able to restore all my personal data though, so doing a factory reset wasn't that bad for me.

Data recovery, how to mount messed up /data - Internal SD - sda25 in Recovery/ADB

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)

Categories

Resources