htc one s tmobile us
I have bootloader and fastboot unlocked
I have recovery (official cwr touch) and adb functionality
I have ROM and adb functionality
Its the first build of cm9 without 1. sdcard mount 2. USB_lun0 3 mobile access or 4 wifi. I know... pretty ****ty place to be. But it is what it is
I've been trying to 1 create symlink between system and sdcard and then mount it.... so I can push a ROM to it and then flash it...or so I can push my backup file back in it and then mount with clockwork and restore... I even tried pushing a modaco ROM to /data/ and then try "recovery --update_image /data/mod.zip" but of course cwr isn't amon-ra and will not allow for flashing from anyplace but sdcard
I can write **** to sdcard....I just cannot get it mounted in recovery or Usb .I wiped my sdcard from fastboot "clear storage" and have tried many things. But that's irrelevant because do have my original Nannie saved to my computer...
I can write/push/files to sdcard... I just cant get the phone to see it.
I need help to 1 access sdcard and boot a normal ROM or 2 fastboot a Nannie back in but that's not possible without plain .img files or 2 somehow boot a ROM from a partition I can see...
I've tried many many things. I can remount it gives me rw when I remount... but the phone or the computer cannot see this...yet.
I even tried RUUing the euro version and of course that failed. I just need to flash a different ROM and the trick is getting the phone or recovery to mount sdcard.
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Fire\tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT24HWxxxxx recovery
C:\Fire\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount failed: Success
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # # echo 1 > /sys/class/usb_composite/rndis/enable
# echo 1 > /sys/class/usb_composite/rndis/enable
~ # # echo 0 > /sys/class/usb_composite/rndis/enable
# echo 0 > /sys/class/usb_composite/rndis/enable
~ # # echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
~ # # echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
~ # ls
ls
boot
cache
data
datadata
default.prop
dev
devlog
emmc
etc
init
init.rc
internal_sdcard
mtdcache
proc
res
root
sbin
sd-ext
sdcard
sys
system
tmp
~ # cd sdcard
cd sdcard
/sdcard # ls
ls
mod.zip
/sdcard # recovery --flash_update mod.zip
recovery --flash_update mod.zip
sh: /sbin/postrecoveryboot.sh: not found
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Fire\tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT24HW408152 recovery
C:\Fire\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount failed: Success
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # # echo 1 > /sys/class/usb_composite/rndis/enable
# echo 1 > /sys/class/usb_composite/rndis/enable
~ # # echo 0 > /sys/class/usb_composite/rndis/enable
# echo 0 > /sys/class/usb_composite/rndis/enable
~ # # echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
~ # # echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
~ # ls
ls
boot
cache
data
datadata
default.prop
dev
devlog
emmc
etc
init
init.rc
internal_sdcard
mtdcache
proc
res
root
sbin
sd-ext
sdcard
sys
system
tmp
~ # cd sdcard
cd sdcard
/sdcard # ls
ls
mod.zip
/sdcard # recovery --flash_update mod.zip
recovery --flash_update mod.zip
sh: /sbin/postrecoveryboot.sh: not found
recovery --flash_update mod.zip
recovery --flash_update mod.zip
exit
exit
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Fire\tools>adb kill-server
C:\Fire\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # mount /sdcard
mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2/dev/block/mmcblk /sdcard
mount -o rw,remount -t yaffs2/dev/block/mmcblk /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount -t yaffs2/dev/block/mmcblk0 /sdcard
mount -o rw,remount -t yaffs2/dev/block/mmcblk0 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount -o rw,remount
mount -o rw,remount
Usage: mount [-r] [-w] [-o options] [-t type] device directory
~ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nodev,noatime,nodiratime,user_xattr,barrier
=1,data=ordered 0 0
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34 /sdcard
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34 /sdcard
mount: Invalid argument
~ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p34
~ #
Sent from my Amazon Kindle Fire using xda premium
maybe you should use code tags in the future to distinguish it from normal text. your post is a little bit confusing because of it's length ...
now to your issue:
boot into cwr
select "mounts and storage" -> "mount /sdcard"
now you can push files to /sdcard/
adb push rom.zip /sdcard/
I get Error to mount sdcard when I try to get CWR to get a file off sdcard
and when I try to mount usb -
Error - no ums_lunfile found
Sorry for being so verbose and wordy, the problem is simple, cant mount, cant get to usb.
Trying to create symlink but I dont see a vold file in here... so I am trying to make one...
this blows -----
only thing left for me to do is wait for RUU or find a boot.img and a system.img to fastboot in.
is there anyway to convert the cwr ext4 backups into .img's?
or is there definitely NO way to flash a ROM from /data/ or other partition in clockwork? any other recoveries for the htc one s? amon?
this blows!! if I can find a usable vold.fstab to use or some way to mount sdcard in recovery I would be all set!! but theres no way to mount sdcard or even ums_lunfile.
Will have to either figure something out but I would appreciate direction. thanks.
im on gtalk at joshcues
Can you boot into the os? If you can have you tried automount from the market. No experience with a phone with no external sdcard yet so i don't know if that will help at all tbh. My wife just got one so i guess I'll be learning now
automount just saves you a couple steps when you plug the device into the computer -- so you dont have to enable usb mount..although i am now trying a bunch of apps.
Yes I can boot into OS -- ive been trying different vold files... no luck so far. I can install any app I want, Ive been using stericsons Remount and Android Root Toolkit Beta https://play.google.com/store/apps/details?id=sa.root.toolkit&feature=search_result to quickly remount rootfs as rw... but it never sticks -- still, they are helpful... at least i have full adb control and am able to play with droid explorer because i am all adb'ed out for now.
if only I could at least enable wifi or get the radio going.. i would be fine with the phone without a sdcard... its kind of funny... but yes i can boot into OS, but
androidcues said:
or is there definitely NO way to flash a ROM from /data/ or other partition in clockwork?
Click to expand...
Click to collapse
did you try to make a link from /sdcard to /data/sdcard/?
mkdir /data/sdcard
ln -s /data/sdcard/ /sdcard/
if that does not work it would be interresting to know what your friend did to the device. have you tried to manually mount the sdcard?
[URL="http://pastebin.com/UMtJK88h"][URL="http://pastebin.com/xBH4Wge3"]http://pastebin.com/YUsCQsrf[/URL][/URL]
Ive got data/sdcard symlink set up and mounted. But recovery cannot flash or restore from data/sdcard. The first time I had the regular mnt/sdcard that I restored from.... but this time I cannot find mnt/sdcard.
Made link to /system/sdcard but cant make it pop up in recovery...
All thats left for me is to find either the fresh rom waiting to be flashed OR the two backups waiting to be restored that reside on sdcard. So, the last thing to do is to get sdcard to freaking pop up in clockwork recovery.
i got somewhere... but not quite at the finish line. Any suggestions? do I need to rebuild the sdcard file system from scratch? Will check back sometime this week... but golly...
jodue said:
did you try to make a link from /sdcard to /data/sdcard/?
mkdir /data/sdcard
ln -s /data/sdcard/ /sdcard/
if that does not work it would be interresting to know what your friend did to the device. have you tried to manually mount the sdcard?
Click to expand...
Click to collapse
I am now able to see sdcard from the phone using file manager and adb -- there is a /data/sdcard/ now that is read write and has a nandroid waiting for me as well as a fresh modaco.zip rom
However I still cannot mount sdcard manually and when I get to recovery it is looking for sdcard in /mnt/sdcard/ not /data/sdcard/
androidcues said:
I am now able to see sdcard from the phone using file manager and adb -- there is a /data/sdcard/ now that is read write and has a nandroid waiting for me as well as a fresh modaco.zip rom
However I still cannot mount sdcard manually and when I get to recovery it is looking for sdcard in /mnt/sdcard/ not /data/sdcard/
Click to expand...
Click to collapse
as i said before ... why don't you just make a link /sdcard that points to /data/sdcard ?
ln -s /data/sdcard /sdcard
how would you do that? can I create a link using adb? I'm in the same situation except that I formatted my system folder because I had no idea mounting wouldn't work (I"m coming from a different phone).
Thanks in advance.
I tried to create a link using
Code:
adb shell
ln -s /data/sdcard /sdcard
no luck. any other idea?
jodue - I can (and have) link I can see sdcard file (with a modaco rom zip waiting on it, as well as clockwork/backup/2012-5-1xxxx) from the following links -
/data/sdcard
/system/sdcard
i sometimes have them written as mnt/sdcard but they never survive a boot.
I unable to mount sdcard in recovery using either or both of those links
I do not (yet) know how to manually add a ums_lunfile to a ROM that does not yet have it incorporated.
I have played with the permissions, looking at my other devices and seeing how other versions of ROMs have different permissions on the same app I am missing a vital switch that will allow Clockworkmod to see the sdcard. The phone may not be seeing the sdcard but it is definitely there, but cant I try to create a link between the Recovery and the sdcard?
I have messed with the vold.fstab and build.prop files in many many different ways (always restoring to default files after each attempt)
I do not (yet) know how to enable wifi on a ROM that does not yet have it incorporated.
I do not (yet) know how to enable bluetooth on ROM that does not yet have it incorporated.
I do not (yet) know how to enable the mobile connection on a ROM that does not yet have it incorporated.
So either I am going to figure out the top three items, or I am going to figure out how to mount my sdcard or have Clockworkmod recognize my SDcard so it can simply 1. restore back to normal or 2. flash a proper zip file.
It is like this phone is on perpetual vacation unless a number of things happen.... kind of funny...Id really like to fix it before the RUU comes out because once it does.. thatll be a lot of searching (Im now trying the Bing search engine because Google didnt find the answer) for nothing!
LuckyMethod said:
I tried to create a link using
Code:
adb shell
ln -s /data/sdcard /sdcard
no luck. any other idea?
Click to expand...
Click to collapse
did you mount and as root?
it's probably the best and simplest solution for you guys to reflash with a stock RUU. i am sure that it's possible to restore a backup from the state you are in however it's hard without actually having the device in front of me ^^
good luck!
bored of waiting for ruu -- another effort
allrighty just logging some more efforts to my morbid problem - the goal was to boot into recovery and then mount..
mount /dev/block/mmcblk0p36 (36 wasnt there, tonight it was mmcblk0p34) /sdcard
or
mount -o bind /data /sdcard
i was able to make both succeed (in recovery) but clockwork did not agree, so thus unable to mount sdcard in recovery so I could restore or flash a proper rom.
I then tried flashing diff recoveries... to eliminate the off chance that it was a problem with particular cwm builds... i flashed stock recovery and then tried to make it flash rom from "internal" storage but of course HTC has that stock recovery looking for very specific files... so my "update.zip" went nowhere (pushed to both /data and /system as im not surre where it flashes from....
then i tried the modaco unofficial cwm nontouch recovery -- that did not want to mount...
then i tried the official cwm nontouch 5831 recovery (the touch recoveries take up space and I cant see the logfile in those)
i think i got somewhere with the mounting in recovery -- i wasted too much time trying to mount in runtime (upon boot) --
next ideas or where shall I go from here? Im not done by any means... anyone happen to know exactly what file the STOCK recovery is looking for when it tries to "flash update from internal storage"
any ideas, i will try. Heres a bunch of pastebins...http://pastebin.com/eTJuJuy9 and http://pastebin.com/0vUdaLvB and http://pastebin.com/qUSJMLpn and http://pastebin.com/fGkHzgbw and i am going to try some more on my windoze 8 system at home because the usb twatholes on this machine are pretty much unreliable.
steps -- I could find out if my mounting and binding needs more followup, I could find a system.img to fastboot I could find a way to flash from /data I could find a way to freaking mount another external drive I could pray like crazy that AmonRa gets a HTC One S and puts his flashable-from-anyplace-other-than-sdcard awesomeness on it....but thats about as crazy as the thought of a HTC guy dropping in here and asking me if I would mind testing his RUU.
cheers and thanks for whatever ideas you have no matter how crazy they sound. Waiting for a RUU is about as much fun as waiting for water to boil.
this is resolved.
lesson to be learned -- flashing an alpha build of a "work in progress" rom without the ability or proper OS to create your own .img files is going to 1. break things 2. cause silly threads like this, 3. force you to learn a lot more about android file systems and 4. wait for a RUU that may never come
xkonni was so kind to make me an updated system.img and accompanying boot.img from which I flashed through fastboot and then that was that.
htc sense makes no sense... but it makes no sense to recklessly flash files without reading the thread itself!! although I am just overjoyed I dont have to see sense again!
hey,
i have the identical problem and i am trying hard to solve this. but till now, i wasnt´t successfull. Is it possible that i use the files? It seems worth a try.
thx
---------- Post added at 11:44 PM ---------- Previous post was at 11:13 PM ----------
i now see that it is impossible to resore any nandroid backup in recovery, because CW doesnt find the sd-card, mounting and usb mounting doesnt´t work,too.
but the crazy thing is: after formating the sd-card i have access in windows but still not in recovery
So, let me get this straight --
You had this same issue -- could not get clockwork to see sdcard much less mount it or access sdcard?
When you were in Android you could not see sdcard or system would not see sdcard?
When you were in ADB you could see sdcard and mount it but it would never stay mounted? Did you try #mount -o bind? did you try to create link to sdcard? (of course did you mount as read/write first?) If so, let me know
You PM'd me and told me about a successful RUU you found that solved it... thats great -- but do you know why trhe problem happened in the first place?
The first time.. it was probably because I flashed a total alpha rom and shouldnt have...
but now.. it happened after I was already established..
I dont know why it happened.... I just know how to get out of it. Last night I got the flash itch and wanted to see what MIUI was up to and once again I ventured out into miui and once again I got bit hard. All of a sudden (I may have accidentially erased sdcard from one of those settings or wiped it) I could not see sdcard.... so i boot into clockwork and lo and behold.. clockwork was up to its old tricks of "cant mount sdcard!!!" and "no umslun0file!!!!" so I was like wow, whats going on?
I want to know WHY this is happening... the "fix" is there, but i dont know why this is happening.
Two things -- 1. This kind of problem has existed but most devices have removable sdcards. so its easy to give up and get a new sdcard.. etc... (problem doesnt get solved it gets trashed) but now... this problem needs to be resolved.. is there a defect? if so.. then how can we resolve these defects without having to replace the entire phone?
partitioning
yesterday... while in CM9... I decided that I wanted to try a repartition. So i pull all files from sdcard onto my desktop. Then I tried to format sdcard with Windows 8. Bizarre thing -- the computer could mount sdcard and all.. but then I got an error when I tried to do a simple format with Windows it wouldnt do it... I shrugged and booted into recovery and had clockwork do the partition...
i set my partition limits and then it proceeded to partition.. but it was "finished partitioning" less than 2 seconds later. I thought that was odd it should take at least a few moments. So maybe Clockwork could not partition or it did not? I dont know yet.
What benefit do phones with built in solid state drives or nonremovable sdcards have? Whats the point? I never had an issue with any of the dozens of sdcards -- some failed, but i simply got a new one or fixed it.
Hello guys,
I recently installed CWM on my GoClever device.
Booting into recovery from Android using ROM Manager didn't work, so I tried
Code:
su "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
And I booted in CWM right after it rebooted
but when I tried to boot the device back to Android, it booted to CWM.
Also the CWM is unable to mount any of the directories.
Code:
CWM-based Recovery v6.0.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /open/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
ADB should work I guess
Could anyone help me please? I guess it's not hard to fix this, probably some file modifying, but I don't really know what exactly to do... :/
EDIT: A recovery image that boots into Android instead of recovery would be a neat solution, but I'm not sure if it's possible
LAST EDIT [SOLVED] :
hajdulak said:
So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it
-> [SOLVED] pretty please
Click to expand...
Click to collapse
Well, i guess A13's will never get some solid support... At least I got my 10 posts... Weeee!
Guys, what's with all the views and no answers?
After some googling, I found out it's quite a frequent issue, but none of the googled threads helped in any way... Damn it...
Also, A13 devices have SOOOOO low support...
And an important thing
I got a dumped stock recovery img on the /sdcard/, just need to know if I can flash it and how to flash it using ADB, I'm quite afraid of doing anything now
Soooo...
When the device is plugged in, it identifies itself as "MID08"
Seems i installed a wrong recovery image
Now I need drivers for my TAB, as it can't appear in the
Code:
adb devices
menu... :/
If anyone can really help, this is a list of my blockdevices:
Code:
loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 nandf ram0 ram1
And this is my fstab
Code:
/dev/block/nandh /cache ext4 rw
/dev/block/nande /data ext4 rw
/dev/block/nandi /emmc auto rw
/dev/block/nandd /system ext4 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
And this is recovery.fstab
Code:
# mount point fstype device
/boot emmc /dev/block/nandc
/cache ext4 /dev/block/nandh
/data ext4 /dev/block/nande
/emmc auto /dev/block/nandi /dev/block/nandi1
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/nandd
/recovery emmc /dev/block/nandg
Also when I try to cd to some dirs i get can't cd to XXX
I guess there's some script that does the mounting stuff, but I still don't know what it is... I just need to access my sdcard and get the recovery image outta there...
So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it
From this thread: https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559, the TrebleCheck app indicates we need an arm64 "a-only" ROM. The Palm Phone is running vendor version 8.1.
Step 1: Download Sugar. This thread: https://forum.xda-developers.com/android/general/release-root-palm-phone-t4021201, has everything you need to know about Sugar. I ran the upgrade once to download the full stock ROM (make a backup as described). Warning, this erases all of your data.
Step 2: Follow this guide: https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473, to build a TWRP for the Palm Phone without source. I used the latest TWRP for the Asus Nexus 7 2013 LTE as my base. From your Palm upgrade backup, the recovery image is the one that starts with 'R', about 36MB. Rename your new TWRP image to match the stock recovery and replace it similar to the rooting guide for replacing the boot image.
Update: snoopy20 has shared his TWRP image here: https://forum.xda-developers.com/showpost.php?p=82654073&postcount=26
Step 3: Extract the system image you downloaded and rename and replace the stock system image. It's the largest file in your Sugar device folder.
Step 4: Re-run the upgrade in Sugar with your replaced images in place.
Step 5: You're probably stuck in a boot loop. Press and hold the power button until you get into recovery, which is now TWRP. First, I formatted data. Then push or otherwise copy this zip to the device: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and install it from TWRP. The stock configuration should be fine, i.e. don't worry about re-naming the zip. Note, do NOT use adb sideload, since that seems to wreck the zip installer's ability to use its own file name to configure itself.
Update: The Universal dm-verity zip may not always work, in particular on AOSP Android 10 images. In this case, you can use another Android device and Magisk Manager to patch the Palm boot image. Push the boot image from your Palm backup (described in Step 1) to the other Android device. It's the mbn file that starts with 'B'. I chose to rename it to boot.img for easier use. Than use Magisk Manager to patch it. Push the modified boot image back to the Palm (in TWRP) and use TWRP to Install->Image it.
Step 6: Reboot! Wipe data and cache for good measure, and you should be set!
All credit goes to the folks from the links above for creating the Treble system image, TWRP guide, and dm-verity script. Thanks to snoopy20 for his TWRP image.
Things that work so far:
* Almost everything
Doesn't work
* Soft key requires an app, such as Key Mapper, to use
* Screen auto brightness is missing
Can you post the TWRP you created?
snoopy20 said:
Can you post the TWRP you created?
Click to expand...
Click to collapse
Is it kosher to publicly post a TWRP created like this (i.e. not from source)?
Additionally, I'm not entirely confident I didn't screw something up, so I'm a little wary to risk everyone's device. Specifically, I do not know what would happen if you get caught in a boot loop and don't have a functioning recovery to boot into in order to restore...
Yeah you just write "Unofficial" or something in the title. Right now I'm happy to brick the Palm, I'm 99% of the way to dropping it but it would be fantastic if I can get a stock Android on it.
By the way do the restrictions, i.e wifi tethering, get applied by the Vendor package?
snoopy20 said:
Yeah you just write "Unofficial" or something in the title. Right now I'm happy to brick the Palm, I'm 99% of the way to dropping it but it would be fantastic if I can get a stock Android on it.
By the way do the restrictions, i.e wifi tethering, get applied by the Vendor package?
Click to expand...
Click to collapse
Hard for me to test since I don't have a supported SIM, but the tethering menu is available in Settings. You'll have to try it and let us know.
If you post the TWRP I'll do so. My biggest concern is if I **** up building it. I sent you a PM.
snoopy20 said:
If you post the TWRP I'll do so. My biggest concern is if I **** up building it. I sent you a PM.
Click to expand...
Click to collapse
Just waiting for android file host to approve
I've attempted to repack but found:
1. Two fstab files are fstab.qcom and fstab.grouper, don't know if I should delete them but instructions seem to indicate I should.
2. Stock ramdisk folder doesn't have a fstab.* file to copy over.
I ended up with this twrp.fstab. Note the encryption part from /data is gone? Unsure if this is ok.
# mount point fstype device
#twrp.fstab
/system ext4 /dev/block/bootdevice/by-name/system
/cache ext4 /dev/block/bootdevice/by-name/cache
/data ext4 /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery
/external_sd vfat /dev/block/mmcblk1p1 flags=removable;storage;display="SDCARD"
/usb-otg auto /dev/block/sda1 flags=removable;storage;display="USB-OTG"
Just a big heads up, when trying to connect to the network today (Visible) I noticed that my IMEI was 0000.... I have never successfully connected the Palm phone and while the behavior now is consistent with my issues before, I can't say whether or not flashing the GSI as outlined here erased my IMEI.
Proceed with caution.
I'm not proceeding at all unless you post your twrp or verify the issues I've had creating it.
I read the IMEI is held on another partition, type 'efs'. I can't see Sugar killing it. More likely your fstab options aren't mounting it.
---------- Post added at 06:57 PM ---------- Previous post was at 06:33 PM ----------
Here is a list of all the mountpoints on a working phone. At a guess the IMEI is held in /firmware. Do you have this mounted?
rootfs on / type rootfs (ro,seclabel,size=1358776k,nr_inodes=339694)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1439668k,nr_inodes=359917,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p27 on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/mmcblk0p28 on /vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
none on /acct type cgroup (rw,relatime,cpuacct)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1439668k,nr_inodes=359917,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/mmcblk0p52 on /fotadata type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p29 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/mmcblk0p12 on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/mmcblk0p1 on /firmware type vfat (ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p30 on /persist type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1439668k,nr_inodes=359917,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
tmpfs on /sbin type tmpfs (rw,seclabel,relatime,size=1439668k,nr_inodes=359917,mode=755)
/sbin/.magisk/block/persist on /sbin/.magisk/mirror/persist type ext4 (rw,seclabel,relatime,data=ordered)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/dm-0 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered)
/sbin/.magisk/block/system on /sbin/.magisk/mirror/system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/sbin/.magisk/block/vendor on /sbin/.magisk/mirror/vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
/sbin/.magisk/block/data on /sbin/.magisk/mirror/data type ext4 (rw,seclabel,relatime,discard,noauto_da_alloc,resuid=10010,data=ordered)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid)
The original firmware recovery has the /firmware mounted as the sdcard so depending on how you mounted for twrp could you have wiped it?
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,verify
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/fotadata /fotadata ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait,verify
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check
/dev/block/mmcblk0p1 /sdcard vfat nosuid,nodev wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/fsg /fsg emmc defaults defaults
Added my TWRP to the OP
OK I've compared and I can't see anything major. The only thing you do have is a few more mount points which I've not had in mine (listed). Where are they from? I think mounting the sdcard (modem firmware) is a bad idea so I'm going to skip that.
/sbl1 emmc /dev/block/bootdevice/by-name/sbl1
#/sbl2 emmc /dev/block/bootdevice/by-name/sbl2
#/sbl3 emmc /dev/block/bootdevice/by-name/sbl3
/tz emmc /dev/block/bootdevice/by-name/tz
/rpm emmc /dev/block/bootdevice/by-name/rpm
/aboot emmc /dev/block/bootdevice/by-name/aboot
#/sbl2b emmc /dev/block/bootdevice/by-name/sbl2b
#/sbl3b emmc /dev/block/bootdevice/by-name/sbl3b
#/tzb emmc /dev/block/bootdevice/by-name/tzb
#/rpmb emmc /dev/block/bootdevice/by-name/rpmb
#/abootb emmc /dev/block/bootdevice/by-name/abootb
#/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=removable;storage;display=USB-OTG
/external_sd vfat /dev/block/mmcblk0p1
/usb-otg auto /dev/block/sda1
So, I have twrp installed, and a fast bootloop almost instantly on start. I haven't been able to solve it thus far. I can get into twrp which is something though.
snoopy20 said:
OK I've compared and I can't see anything major. The only thing you do have is a few more mount points which I've not had in mine (listed). Where are they from? I think mounting the sdcard (modem firmware) is a bad idea so I'm going to skip that.
/sbl1 emmc /dev/block/bootdevice/by-name/sbl1
#/sbl2 emmc /dev/block/bootdevice/by-name/sbl2
#/sbl3 emmc /dev/block/bootdevice/by-name/sbl3
/tz emmc /dev/block/bootdevice/by-name/tz
/rpm emmc /dev/block/bootdevice/by-name/rpm
/aboot emmc /dev/block/bootdevice/by-name/aboot
#/sbl2b emmc /dev/block/bootdevice/by-name/sbl2b
#/sbl3b emmc /dev/block/bootdevice/by-name/sbl3b
#/tzb emmc /dev/block/bootdevice/by-name/tzb
#/rpmb emmc /dev/block/bootdevice/by-name/rpmb
#/abootb emmc /dev/block/bootdevice/by-name/abootb
#/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=removable;storage;display=USB-OTG
/external_sd vfat /dev/block/mmcblk0p1
/usb-otg auto /dev/block/sda1
Click to expand...
Click to collapse
I think the guide for porting TWRP mentioned to add it, so I did.
snoopy20 said:
So, I have twrp installed, and a fast bootloop almost instantly on start. I haven't been able to solve it thus far. I can get into twrp which is something though.
Click to expand...
Click to collapse
Sounds similar to me. Did you flash the new system as well? If so, this is when you use TWRP to flash the zip to disable dm-verity.
I did, then the dm-verity but with no success. Assuming /system was corrupt or wrong I've deleted it. I'm now trying to work out how to flash the system.img without fastboot (which I don't have).
So far dd is ending up with a corrupt partition and twrp insists on a zip for system flash. Trying to figure out how to convert it.
---------- Post added at 09:44 PM ---------- Previous post was at 09:26 PM ----------
I did, then the dm-verity but with no success. Assuming /system was corrupt or wrong I've deleted it. I'm now trying to work out how to flash the system.img without fastboot (which I don't have).
So far dd is ending up with a corrupt partition and twrp insists on a zip for system flash. Trying to figure out how to convert it.
Actually you said you tried 10 unsuccessfully, so how did you then flash the v8 image?
snoopy20 said:
So far dd is ending up with a corrupt partition and twrp insists on a zip for system flash. Trying to figure out how to convert it.
Click to expand...
Click to collapse
TWRP doesn't say "Install Image" at the bottom when you go to Install?
Actually you said you tried 10 unsuccessfully, so how did you then flash the v8 image?
Click to expand...
Click to collapse
I'm assuming the 2nd link down in OP (github).
This is exciting!
Anytime I got stuck, from TWRP I used
Code:
adb reboot edl
then I used Sugar to reflash everything all over again.
Phew, I didn't know about that one. I'll try again.
You can't flash an img from TWRP, there's no boot partition to enter fastboot mode.
I'd originally downloaded the nogapps without su and added Magisk.zip after, this caused an instant bootloop. The one with build in gapps+su works. It's possible to disable all gapps and related services except GoogleOne (I installed OpenLauncher into /system/app then removed GoogleOne by force). After this "Google" can be removed and all notifications about Google Services end.
I recommend you take down the twrp and remove the line which mounts the firmware partition as sdcard in case this is what wiped your IMEI. I build my own without this line and IMEI survived.
Tested
Wifi hotspot is working!
Bluetooth, camera, all USB,
Stability
Not working
Thee dots button (don't think it's a big deal as you get the three icons for back etc by default).
Auto screen brightness