• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM10 Development (moved to upp)

Dm47021 said:
reinstall cm10, then flash that kernel. do not reboot until you have flashed both
Click to expand...

That's exactly what I did, clear caches and factory reset, re-install cm-10 follow by the kernel without rebooting and nothing


Edit: after a little while the black screen went off and the red led turned on
 
partitions are still set wrong, in the init.rc as well. if the phone thinks the cache partition is the data partition, some unknown partition(possibly carrier) is the cache partition, and the data partition is mounted as the carrier partition, would that cause it to not boot?
 
Dm47021 said:
yeah the partitions are all messef up. fstab says 12 is boot. init.rc says its /system
Click to expand...

ok, here are the real partitions that i know of

/boot emmc /dev/block/mmcblk0p12
/recovery emmc /dev/block/mmcblk0p13
/system ext4 /dev/block/mmcblk0p15
/cache ext4 /dev/block/mmcblk0p18
/data ext4 /dev/block/mmcblk0p19
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2
/carrier ext4 /dev/block/mmcblk0p16
/persist ext4 /dev/block/mmcblk0p7 ?

still unsure about persist, but 16 is carrier, so this table should be the exact partition layout of the phone with the correct file systems and everything
 
boot actually is 12, system is 15, recovery is 13, cache is 18, data is 19, we know those partitions as well as the sd card for certain. i have tested all of those values myself
the zte rom had them labeled differently however, and even force mounting 17 would give you cache, 18 data, and 19 carrier i believe dont remember, 19 is 2.7gb in the partition table though, that is the size of our data partition, and force mounting 19 in cwm gives you the data partition. its all very confusing, but you can thank zte for that
 
basically the reason why im going through telling you all this tho is because within the rom the partitions were different than outside so although im pretty sure that was only because of the zte rom it might effect any rom using their kernel as a base or any rom on the phone period, i dont know exactly how they managed to flip flop everything but id start with trying the REAL partition values as apposed to ztes fake ones
 
my partitions file i pulled from the phone in case it helps, it certainly helped me tell what was the real data partition

major minor #blocks name

7 0 2111 loop0
179 0 3817472 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 32768 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 516096 mmcblk0p15
179 16 57344 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 311296 mmcblk0p18
179 19 2736128 mmcblk0p19
179 32 31166976 mmcblk1
254 0 2110 dm-0
 
seems to me by that 16 might actually be carrier, not sure tho

edit: 16 is 50mb unaccounted for, 9 and 10 are both 30mb unaccounted for, and the rest seem like just 8mb filler
 
ok, i double checked and 16 is carrier, so the only thing not figured out is 9 and 10 which dont seem to be anything but a total of 60mb of wasted space
edited my table above to match my findings
 
Dm47021 is putting something together...I know it is hard for all of us but we need to be patient and let the man do his work :)
 
me too, i was trying all day to get my build system up so i could tinker a bit myself but all i managed to do is figure out what not to do to a linux machine... never ever ever change persmissions on /etc/sudoers it will break your shit lol. luckily i was able to boot into recovery mode and fix it but that could have been really really bad

and for those of you wondering why in the hell i would do such a stupid thing. i got sick and tired of always having to sudo everything and having sudo not run things the same way and so i said screw you ubuntu. i went to the root of the filesystem and did this...

sudo chmod a+rwx -R *

which basically means make everyone able to read, write, and execute everything on the linux system. baaaad idea, kuz i then found a way that supposedly let me take root permissions at all times which didnt work as it turns out but i figured it was easier than waiting for the entire file system to chmod and restarted to try it out but the chmod had reached the file in question and ubuntu doesnt like it when the permissions of that file are changed at all. so i couldnt even sudo anything at that point
 
now im stuck back at the part where i need an adb connection and my rules file isnt working for me. i cant win with this damned thing
 
ok so looking in the officially supported device trees

i saw this in the manta's full_manta.mk file

PRODUCT_PROPERTY_OVERRIDES := \
net.dns1=8.8.8.8 \
net.dns2=8.8.4.4

i know that my dns for connecting through the phone is 1.2.3.4
and i know that data isnt working on the warp even with the joe stone ril files
could it be the dns just wasnt set up correctly so the phone cant look anything up???
or is it actually a problem with the ril files themselves?
i dont have any idea what is going on with it obviously, ive never used a warp one let alone one with cyanogen on it, but im just throwing it out there just in case someone missed it
 
@junkie2100 if you want me to build something for you, please let me know. I normally have time on my hands and lately spend most of it watching an empty thread :(
 
You must log in or register to reply here.
Back
Top Bottom