[28-06] [ROM] TripNDroid Revised - Endeavor Unleashed | 015

Search This thread

itshotinhere

Senior Member
Sep 13, 2009
419
68
Not sure if this helps at all...

rootfs / rootfs rw,relatime 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,
noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/RCA /rca ext4 ro,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/RFS /rfs ext4 rw,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DLG /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordere
d 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,n
oauto_da_alloc 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=
1 0 0
/dev/block/vold/179:14 /storage/sdcard0 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:14 /mnt/secure/asec vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
 

pandaball

Inactive Recognized Developer
Oct 18, 2011
2,388
1,735
Not sure if this helps at all...

rootfs / rootfs rw,relatime 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,
noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/RCA /rca ext4 ro,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/RFS /rfs ext4 rw,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DLG /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordere
d 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,n
oauto_da_alloc 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=
1 0 0
/dev/block/vold/179:14 /storage/sdcard0 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:14 /mnt/secure/asec vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

Wow. Somehow all the important partitions (system, data etc) are accessible to nothing and nothing at all (except superuser maybe). No read, write or execute access. Permissions are all wrong. Since chown and chmod don't quite work, you might have to rewrite all the partitions, which isn't possible at this time until s-off or the sbk is obtained.
 

itshotinhere

Senior Member
Sep 13, 2009
419
68
Wow. Somehow all the important partitions (system, data etc) are accessible to nothing and nothing at all (except superuser maybe). No read, write or execute access. Permissions are all wrong. Since chown and chmod don't quite work, you might have to rewrite all the partitions, which isn't possible at this time until s-off or the sbk is obtained.

What would a normal result of 'adb shell mount' look like? Can this be corrected at all?

EDIT: These are the results from recovery...

rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p14 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p14 on /and-sec type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p13 on /cache type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
 
Last edited:

dotzeno

Member
Feb 12, 2010
39
5
Hong Kong
Code:
~ # busybox mkfs.vfat /dev/block/mmcblk0p14 28672
busybox mkfs.vfat /dev/block/mmcblk0p14 28672
No changes after.
This also applies to me.


Try this

within recovery, not sure if you need to mount first

adb shell

mke2fs -j /dev/block/mmcblk0p13
mke2fs -j /dev/block/mmcblk0p12
mke2fs -j /dev/block/mmcblk0p15
Tried this, but changed nothing.

I have attached my last_kmsg and logcat, hoping it will help.
 

Attachments

  • logcat.txt
    44 bytes · Views: 2
  • last_kmsg.txt
    63.9 KB · Views: 6
Last edited:

pandaball

Inactive Recognized Developer
Oct 18, 2011
2,388
1,735
What would a normal result of 'adb shell mount' look like? Can this be corrected at all?

EDIT: These are the results from recovery...

rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p14 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p14 on /and-sec type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p13 on /cache type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)

It's really strange, because recovery should be able to write to /system, /data etc even when Android cannot. Recovery did not show the permissions of /system, /data and /cache so I can't be sure why nothing is writeable, even when in fastboot.
 

Sckank

Senior Member
Jul 7, 2010
2,076
427
Florø
Re: [24-01] [ROM] TripNDroid CM 10.1 - Endeavor Unleashed | 003 | TRUE OTG

Wow Trip is still trying to help ppl out!!! :thumbup:
I'm impressed! :) :thumbup:
Hope all of you can find a way out!!!!
 
  • Like
Reactions: theDroidfanatic

theDroidfanatic

Senior Member
Apr 24, 2012
7,552
5,729
Jeddah
www.twitter.com
Re: [24-01] [ROM] TripNDroid CM 10.1 - Endeavor Unleashed | 003 | TRUE OTG

Can anyone please tell me how is the pictures' quality with latest version? Thanks.

Don't flash latest version! It could brick your phone, but Trip made some epic discoveries, so a fix should be here apk. :)

Use 002 for now

Sent from my One X running Blade v4.6.0. At a mere 240 MB, with tons of AROMA Mods and tweaks, this, is what you want.
 
  • Like
Reactions: reneftw

farhanito

Senior Member
Aug 21, 2010
901
231
Jakarta
everytime i went to recovery (TWRP), i got these

Updating partition details...
E:Failed reading /dev/block/mmcblk0p17
(I/O error)
E:Failed closing /dev/block/mmcblk0p17
(I/O error)
E:Failed closing /dev/block/mmcblk0p17
(I/O error)
E:Unable to mount /cache for OpenRecoveryScript support

to my finding, mmcblk0p17 = "misc"
Code:
c:\Android>adb shell cat /proc/emmc
dev:        size     erasesize name
mmcblk0p5: 00800000 00001000 "recovery"
mmcblk0p4: 00800000 00001000 "boot"
mmcblk0p12: 50000000 00001000 "system"
mmcblk0p13: 14000000 00001000 "cache"
mmcblk0p17: 00200000 00001000 "misc"
mmcblk0p1: 00600000 00001000 "wlan"
mmcblk0p2: 00200000 00001000 "WDM"
mmcblk0p20: 00200000 00001000 "pdata"
mmcblk0p3: 00600000 00001000 "radiocab"
mmcblk0p14: 650000000 00001000 "internalsd"
mmcblk0p15: 89400000 00001000 "userdata"
mmcblk0p19: 01600000 00001000 "devlog"
mmcblk0p16: 00200000 00001000 "extra"
 

LiooO

Senior Member
Dec 7, 2008
118
10
only stupid people thinks custom ROMs come with any sort of guarantee...

Who said anything about guarantee? I didn't said anything even close to that.. I just said that is rather normal to try to help after many people got bricks instead of phones. So next time when you quote me pls try your reply to make some sense?
 

BlueSingA

Senior Member
Dec 24, 2012
493
173
Novi Sad
@itshotinhere I'm not so sure, but shouldn't mmcblk0p13 be also ext4 with data=ordered?
@farhanito Yeah, mmcblk0p17 = "misc" is where the communication between bootloader, recovery and system happens.
 
Why is that wow and why you are impressed i don't get it? It would be crazy if he didn't try to help tbh...

Why do you even post here!? Trip could have lost his inspiration and left. He has no obligations to stay, he is doing this for free. We all know the risk involved with flashing. Sckank gave the thread some positiv energy. You on the other hand did not. Just leave your posts to yourself if you have nothing to say.
 

tmotard

Senior Member
Feb 11, 2008
1,375
325
Paris
I agree.
Bricked my HOX with latest version.
That's the risk.
i appreciate Trip's work & help for the community.

Thanks to him.

will be back asap :) (when my HOX come back from HTC)
 
  • Like
Reactions: theDroidfanatic

mido.fayad

Senior Member
May 14, 2011
641
295
alex
I agree.
Bricked my HOX with latest version.
That's the risk.
i appreciate Trip's work & help for the community.

Thanks to him.

will be back asap :) (when my HOX come back from HTC)

me too my device bricked and i appreciate trip's work alot and his efforts to help people

and can't say anything to him except really thanks alot for ur great work and will continue use ur kernels because they are uniqe and there is no kernel match ur one :)

i sent my device to HTC and they said that it will be fixed in 3 days

hope it come back to try the latest trip sense kernel v003 ;)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 418
    FXzMD4d.png


    TripNDroid Mobile Engineering is proud to hereby announce the release of CyanogenMod 10 for the HTC Endeavoru also known as the HTC One X (Tegra 3 only!)

    Working:
    - Mobile network (data, calls, sms etc.)
    - GPS
    - Bluetooth
    - Bluetooth tethering
    - Wifi
    - Hardware video decoder
    - Hardware acceleration (2D/3D)
    - Audio
    - MIC (recording)
    - NFC
    - Camera (rear and front)
    - Leds (incl. blink)
    - WIFI Hotspot


    Not working:
    - ?

    Features:
    TDF support (kernel + rom)
    Advanced powersaving mode
    Hardware menu key is mapped to recent task button.
    True Jelly Bean kernel
    Build with Linaro toolchain
    Supporting all hboot versions (?)


    Changelog 015:
    - Notepad app
    - TripNDroid settings introduced
    - Some battery icons added
    - New camera app for (HTC)Tegra chipsets
    - including real ZSL (zero shutter lag) support
    - Various bugfixes
    - Custom settings app
    - New wifi firmware
    - Battery led only green when 100% charged
    - Powersave mode will automaticly be activated when temps get to high
    - DSPManager removed
    - Temp monitor (/sys/td_framework/cpu_temp)
    - New TDF kernel (you need to flash boot.img)
    - Kernel HZ=1000
    FULL WIPE IS REQUIRED
    (changelog is incomplete, stay tuned)

    Installation instructions:
    - Extract boot.img from zip file
    - Flash the boot.img manually via "fastboot flash boot boot.img"
    - Go into recovery
    - Format /system
    - Flash the rom
    - Reboot
    - Enjoy TripNDroid CM 10.1

    Screenshot:
    HomXajR.png



    Download rom:
    http://euroshare.eu/file/15628685/tripndroid-endeavoru-ota-eng.noeri-015.zip
    http://tripndroid.bindroidroms.com/tripndroid_endeavoru-ota-eng.noeri_015.zip


    tripndroid mirror is currently offline
    Code:
    http://www.tripndroid.com/downloads/cm10-1/tripndroid_endeavoru-ota-eng.noeri_015.zip

    DONT INSTALL ADDITIONAL GAPPS PACKAGE ON THIS ROM


    Sources:
    https://github.com/TripNRaVeR


    Credits:
    CyanogenMod
    Pabx for echo+call volume fix
    BinDroid for providing webspace

    External information:
    www.tripndroid.com

    Install tutorial by ashwin123:
    http://www.youtube.com/watch?v=elDvcVot7qo

    Video preview by Flow-Wolf:
    40
    I'm talking to my device again within APX, can write and create partitions, bootloader acces, have acces to everything now.

    Will need to look deeper before i'm flashing anything, keeping you in touch.
    31
    Enjoy version 003

    http://tripndroid.bindroidroms.com/cm10_endeavoru-ota-eng.noeri-003.zip

    Changelog 003:
    Incall audio fixes
    Fixed headphone detection
    FileManager added
    Fixed Camera face detection
    rx_wake fixed
    init.d support added
    Jelly Bean kernel (changes below)
    - jRCU
    - Wifi drivers build from source
    - Simple IO scheduler
    - KSM added
    - New TI-ST drivers
    - Bugs fixed


    YOU NEED TO FLASH BOOT.IMG!!!!!
    30
    The 3.1.10 kernel is completely stable after 1 hour and 10 minutes of testing. I'll keep running it the rest of the day to see if it really holds up. I'll leave it idle for hours to see what it does because that is where the hardcore bugs are present.

    LP0 was highly unstable and causing the device to get extremely hot after it was woken up. The last hour i turned it on/off after reasonable amount of time and it enters and leaves LP0 without issues atm.

    Previously the signal was always lost after 30 or more minutes in LP0, screen awake after some time in LP0 was giving hard errors untill you rebooted it. For now all issues are gone.

    Curious to see where it goes. Probably 005 will be with the 3.1.10 kernel tonight.
    27
    Found a proper BT and GPS fix...

    Best thing is that it gives me the option to remove all BT and GPS libs from htc and nvidia. :)
    Meaning no more kernel requirement of TI drivers. Saves space, services and unneeded vendor crap can be removed finally