Discussion in 'Android Devices' started by jimsmith80, Jul 20, 2013.
Is this what your looking for?
A4 is ready for testing
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.
Thats the one. Thank you sir
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.
Here is what I have so far. I just cant find boot
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:/ #
Building now. I am almost sure that A5 will run
A5 is up. Partition table has been fixed. Fingers crossed.
Hung up at Flashing Kernel again.
a5 flashed succesfully but then stock splash then just a black screen with the red led lit up
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
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.
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.
Fixing permissions didnt work
Did u remove any apks?
Nope it's all stock. It could be an issue with the image I built off of
I doubt its the image, these phones won't flash anything through recovery. Neither of our things work and were far from noobs.
Ill look into building twrp. I Luke it more than cmw anyway
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?
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
I'm honestly curious if cmw is working at all
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. TWRP is nice as for you can actually name the nand.
Ima fix cwm now, fix mounts on the fstab and see if we get better results
I successfully flashed 4.2 camera. If that helps