[ROM] DroidSmith_Force - Beta


  1. tgamble160

    tgamble160 Member

    jimsmith80 likes this.
  2. jimsmith80

    jimsmith80 Well-Known Member

    A4 is ready for testing
    tgamble160 likes this.
  3. Golono

    Golono Well-Known Member

    I'm trying it right now. Its been stuck at 'Flashing Kernel' for over five minutes.

    EDIT:After over 20 minutes of being stuck at 'Flashing Kernel' I pulled the battery. Restored the phone with a nandroid backup.
  4. jimsmith80

    jimsmith80 Well-Known Member

  5. jimsmith80

    jimsmith80 Well-Known Member

    Here is where I am stuck. I cant figure out where the boot partition is located. Thats why its getting stuck at the Kernel. I'm going to see if the avid guys can help out.
  6. jimsmith80

    jimsmith80 Well-Known Member

    Here is what I have so far. I just cant find boot

    /dev/block/mmcblk0p18", "/system"

    /dev/block/mmcblk0p22","/data"

    /dev/block/mmcblk0p21 cache
  7. rbheromax

    rbheromax Well-Known Member

    Did you shouldve had partitions before you started.

    But luckily I pulled them last night

    app_86@android:/ $ suev/block/platform/msm_sdcc.1/by-name <sh: bustbox: not found/dev/block/platform/msm_sdcc.1/by-name <lrwxrwxrwx 1 root root 21 Dec 31 1969 aboot -> /dev/block/mmcblk0p13lrwxrwxrwx 1 root root 21 Dec 31 1969 boot -> /dev/block/mmcblk0p15lrwxrwxrwx 1 root root 21 Dec 31 1969 cache -> /dev/block/mmcblk0p21lrwxrwxrwx 1 root root 21 Dec 31 1969 carrier -> /dev/block/mmcblk0p23lrwxrwxrwx 1 root root 21 Dec 31 1969 fsg -> /dev/block/mmcblk0p10lrwxrwxrwx 1 root root 21 Dec 31 1969 grow -> /dev/block/mmcblk0p24lrwxrwxrwx 1 root root 21 Dec 31 1969 misc -> /dev/block/mmcblk0p19lrwxrwxrwx 1 root root 21 Dec 31 1969 modem -> /dev/block/mmcblk0p14lrwxrwxrwx 1 root root 21 Dec 31 1969 modemst1 -> /dev/block/mmcblk0p11lrwxrwxrwx 1 root root 21 Dec 31 1969 modemst2 -> /dev/block/mmcblk0p12lrwxrwxrwx 1 root root 20 Dec 31 1969 persist -> /dev/block/mmcblk0p8lrwxrwxrwx 1 root root 21 Dec 31 1969 recovery -> /dev/block/mmcblk0p16lrwxrwxrwx 1 root root 20 Dec 31 1969 rpm -> /dev/block/mmcblk0p4lrwxrwxrwx 1 root root 20 Dec 31 1969 sbl1 -> /dev/block/mmcblk0p1lrwxrwxrwx 1 root root 20 Dec 31 1969 sbl2 -> /dev/block/mmcblk0p2lrwxrwxrwx 1 root root 20 Dec 31 1969 sbl3 -> /dev/block/mmcblk0p3lrwxrwxrwx 1 root root 21 Dec 31 1969 splash -> /dev/block/mmcblk0p17lrwxrwxrwx 1 root root 20 Dec 31 1969 ssd -> /dev/block/mmcblk0p9lrwxrwxrwx 1 root root 21 Dec 31 1969 system -> /dev/block/mmcblk0p18lrwxrwxrwx 1 root root 21 Dec 31 1969 tombstones -> /dev/block/mmcblk0p20lrwxrwxrwx 1 root root 20 Dec 31 1969 tz -> /dev/block/mmcblk0p5lrwxrwxrwx 1 root root 21 Dec 31 1969 userdata -> /dev/block/mmcblk0p22lrwxrwxrwx 1 root root 20 Dec 31 1969 ztecfg -> /dev/block/mmcblk0p7lrwxrwxrwx 1 root root 20 Dec 31 1969 ztelk -> /dev/block/mmcblk0p6root@android:/ #
    jimsmith80 likes this.
  8. jimsmith80

    jimsmith80 Well-Known Member

    Building now. I am almost sure that A5 will run
    tgamble160 likes this.
  9. jimsmith80

    jimsmith80 Well-Known Member

    A5 is up. Partition table has been fixed. Fingers crossed.
    tgamble160 likes this.
  10. Golono

    Golono Well-Known Member

    Hung up at Flashing Kernel again.
  11. tgamble160

    tgamble160 Member

    a5 flashed succesfully but then stock splash then just a black screen with the red led lit up
  12. jimsmith80

    jimsmith80 Well-Known Member


    How long did you wait after the splash screen. It takes about 5 minutes for gingerbread to boot the first time, so I would think it would be about double for ics
  13. Golono

    Golono Well-Known Member

    After being hung up at Flashing Kernel, I tried pulling the battery and booting and had the same result. Android logo then black screen with red indicator light.
  14. jimsmith80

    jimsmith80 Well-Known Member

    Everything should be in the right place. It must be an issue with the permissions. I doubt this will work but you could try running fix permissions. Ill do some work on the uppdater scrip. I hope to have something that runs soon.
  15. tgamble160

    tgamble160 Member

    Fixing permissions didnt work
  16. rbheromax

    rbheromax Well-Known Member

    Did u remove any apks?
  17. jimsmith80

    jimsmith80 Well-Known Member

    Nope it's all stock. It could be an issue with the image I built off of
  18. rbheromax

    rbheromax Well-Known Member

    I doubt its the image, these phones won't flash anything through recovery. Neither of our things work and were far from noobs. :confused:
  19. jimsmith80

    jimsmith80 Well-Known Member

    Ill look into building twrp. I Luke it more than cmw anyway
    tgamble160 likes this.
  20. rbheromax

    rbheromax Well-Known Member

    Perfect, can you mount "by-name" and "mmcblk*p*" at the same time to be flexible with our install scripts? If not what are you going to use as mounts in the fstab?
  21. jimsmith80

    jimsmith80 Well-Known Member


    I'm honestly not sure. Before yesterday I have never seen an updater script that used the by-name method, but now that we know the partition mapping it shouldn't matter
  22. jimsmith80

    jimsmith80 Well-Known Member

    I'm honestly curious if cmw is working at all
  23. sonicbluemustang

    sonicbluemustang Well-Known Member

    I believe that could be the case with this CWM. It will backup and restore but I tried to flash something once and seen no result. :confused: TWRP is nice as for you can actually name the nand.
  24. rbheromax

    rbheromax Well-Known Member

    Ima fix cwm now, fix mounts on the fstab and see if we get better results
  25. tgamble160

    tgamble160 Member

    I successfully flashed 4.2 camera. If that helps
    MidshipAc likes this.
Loading...

Share This Page