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

Root [Boost Mobile] Cyanogenmod 7 progress/updates (daily!)

I'm just going to wait until I can get cwm debuggable. Once thats happened I dont need to go thru the trail and error process
 
Quick question.. did any of you guys try editing the tethering prop in the build.prop yet? So we can get the "Tethering & Portable Hotspot" option enabled.
 
I just looked in build.prop, but don't see anything related to tethering. I'm sure there's a setting for it if I google, but at this point we really need to get a working image that actually boots so we can see what errors are being thrown. At this point we're flying blind because there's no way to know what is failing. Hopefully Snake/QuietStorm can get the updated ver of CWM going with the modified adb settings. That may be a big help.

As a side note, I tried the latest build on my phone using the stock boot.img file and the CM7 files, but it didn't work....again! :-( Oh well, at least my phone didn't blow up when I restored my backup. I'm extremely thankful for that!

Snake - Let me know if there's anything I can do to help with CWM.
 
What about this setting in default.prop
425748b2-39bc-4413.jpg
 
Lordvincent 90 said:
HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki
Click to expand...

on that, the split_bootimg.zip file is a 404.. I wish I could do that

edit:
downthemachine said:
What about this setting in default.prop
425748b2-39bc-4413.jpg
Click to expand...

I had to zoom in on that and it was barely legable (sooo small), but actually i needed to set the opposite of those settings..

edit 2: ok here's a question that will solve A LOOOOOOOOOOOOOOOT of confusion: where are the files located that get put into the boot.img in the cm7 output?
 
I'm just so confused at the moment about this whole thing.. i just need to get cwm to enable adb. I was told adb in cwm was enabled by default but its not recognized? I was told that it might be missing the usb serial drivers? I don't know the more that i go into this thing im just getting more and more confused im not sure what I should do now, make cwm debuggable or keep trying different things to make the cm7 boot im just not sure anymore :confused: :confused:

edit: using the phone's boot.img didn't work. What are the files that make cm7.. well cm7 at? I don't want to overwrite them if they are located in the boot.img because then what would be the point?

edit 2:
free your android guide said:
Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
Click to expand...

Completely unexplained how this works thus useless and leads to more confusion which i don't need right now :(

edit 2: I think what would help me a lot is knowing this: what instuctions are being executed most likely where it gets stuck in my case?
i.e. the kernel? init? what? I'm asking so I know what part to focus on changing so that it can actually boot..
basically in what part of the cyanogenmod build does my problem most likely lie in if its getting stuck this early in the boot process

edit 3: what does the system.img contain in /out/target/product/warp? Also if I replace the boot.img in that folder and redo mka -j8 bacon it will remake the cm7 build with the new boot.img file right? I think thats how it works considering thats what I did then checked the md5's on the last output and they were different and plus the fact that it did more. Though, I really do want to know whats in system.img. Also when I extracted the boot.img, I went into the ramdisk/system and there was nothing there..? o:

Also one more thing, whats the difference between the kernel file (no extention) in /out/target/product/warp and the one named boot.img-kernel when I extract the boot.img?
 
Ok I figured out a lot of things and here's some progress: I am going to start looking into making this flashable via nandroid because jbrd400 said that it may be a problem with the rom format period. I am going to see if this will work any better and if so then :D I can't wait to see if it will boot!

I was going to try to make the cm7 kernel for this, but I get some errors:
Code: 
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
#
# configuration written to .config
#
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  CHK     include/generated/utsrelease.h
  UPD     include/generated/utsrelease.h
  CC      scripts/mod/empty.o
cc1: error: unrecognized command line option ‘-mlittle-endian’
cc1: error: unrecognized command line option ‘-mno-thumb-interwork’
  HOSTCC  scripts/mod/mk_elfconfig
scripts/mod/empty.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
scripts/mod/empty.c:1:0: error: bad value (armv5t) for -march= switch
make[2]: *** [scripts/mod/empty.o] Error 1
make[2]: *** Waiting for unfinished jobs....
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/conmakehash
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [scripts] Error 2
make: *** Waiting for unfinished jobs....
  Generating include/generated/mach-types.h

I am using this guide: Building Kernel from source - CyanogenMod Wiki
 
Can't say for sure, but I'd bet these have to do with the toolchain being used.

scripts/mod/empty.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
scripts/mod/empty.c:1:0: error: bad value (armv5t) for -march= switch
 
I'll look into it, I know I did export CCOMPILER=$~/cm7/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- both in just the terminal and pasting it in ./bashrc (via nano ./bashrc) I think.. but I'll try it again
 
If you notice, in the 2nd line it mentions armv5t, which is not the warp. I don't recognize anything from the 1st line either.

Maybe the variable for the toolchain is different when building kernels and building ROMs? (or there's a configuration file somewhere where you have to specify the toolchain or arm type. I dunno. Just a guess based on the output.
 
yeah I'll definitely check that out.. Thanks for helping me notice that lol, i feel kinda dumb now since that was kinda obvious

in other news, cm7 is now in nandroid format!! I'll be testing that out as im installing it as Im typing! Can you believe that, I mean when you read this, knowing that when I'm typing these exact words its installing it :P

edit: This may be a problem.. with the kernel thingy. The contents of empty.c is this: /* empty file to figure out endianness / word size */

So it's being updated in real time im assuming which means I'll have a heck of a time figuring this one out :p lol at this point im just hoping that the nandroid works xD

edit: didn't boot but im going to try out different things

edit 2: I tried to do the export command for the kernel now I get this:

Code: 
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
make: /cm7/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-gcc: Command not found
  CHK     include/linux/version.h
  HOSTCC  scripts/bin2c
  CC      scripts/mod/empty.o
/bin/sh: /cm7/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-gcc: not found
make[2]: *** [scripts/mod/empty.o] Error 127
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
  CHK     include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
  CC      kernel/bounds.s
/bin/sh: /cm7/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2
make: *** Waiting for unfinished jobs....
make: *** [scripts] Error 2
:confused: arm-eabi-gcc is available when I looked in that folder.. tho im not sure whats going on completely

edit 3: I need a COMPLETELY stock boot.img (preferrably one from the b08 update found here: http://androidforums.com/warp-all-things-root/473503-b08-update-file-captured.html But I can't seem to get the link working)
 
Did you specify the "gcc" in arm-eabi-4.4.0/bin/arm-eabi-gcc or did the script append it? I think the toolchain is usually listed as "arm-eabi-4.4.0/bin/arm-eabi-" without gcc on the end. Again, not positive.
 
Snake X said:
yeah I'll definitely check that out.. Thanks for helping me notice that lol, i feel kinda dumb now since that was kinda obvious

in other news, cm7 is now in nandroid format!! I'll be testing that out as im installing it as Im typing! Can you believe that, I mean when you read this, knowing that when I'm typing these exact words its installing it :P

edit: This may be a problem.. with the kernel thingy. The contents of empty.c is this: /* empty file to figure out endianness / word size */

So it's being updated in real time im assuming which means I'll have a heck of a time figuring this one out :p lol at this point im just hoping that the nandroid works xD

edit: didn't boot but im going to try out different things

edit 2: I tried to do the export command for the kernel now I get this:

Code: 
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
make: /cm7/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-gcc: Command not found
  CHK     include/linux/version.h
  HOSTCC  scripts/bin2c
  CC      scripts/mod/empty.o
/bin/sh: /cm7/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-gcc: not found
make[2]: *** [scripts/mod/empty.o] Error 127
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
  CHK     include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
  CC      kernel/bounds.s
/bin/sh: /cm7/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2
make: *** Waiting for unfinished jobs....
make: *** [scripts] Error 2
:confused: arm-eabi-gcc is available when I looked in that folder.. tho im not sure whats going on completely

edit 3: I need a COMPLETELY stock boot.img (preferrably one from the b08 update found here: http://androidforums.com/warp-all-things-root/473503-b08-update-file-captured.html But I can't seem to get the link working)
Click to expand...

I have a completely stock boot.img

Want me to upload it & give you the link?
 
Actually at this point I don't think it matters tbh because I don't think it has to do with the boot.img anymore, i think its the kernel now

EDIT: I think I have good news! The device was recognized!! But not for long :( It disconnected I'll still leave it running though

edit: I rebooted and even though adb didn't recognize it, the computer did via lsusb for like a minute before "disconnecting" again..
 
yeah, im going to see if my latest build works if not then ill convert to nandorid if that doesnt do anything then back to kernel.. :L

edit: Jbrd do you have your own warp?

edit 2: Ok I don't think it likes a boot.img that has been unpacked, edited, and repacked, im not getting the recognization anymore.. though danggit I need to edit the build.prop within it to enable adb...... well I'll try more stuff tomorrow
 
Yeah, I've been testing the nandroid method too and it starts to boot and just reboots after 30-45 sec or so and goes back to CWM. So just the fact that both of our phones are trying to boot via nandroid backup is a step in the right direction. Not saying ROMs are out of the question as I think we had the same issue (reboot to CWM) with one of the ROM builds too. Need to test more. Anyway, now that they are trying to boot, I would agree that looking at the kernel or seeing if there are any specific kernel settings required for CM7 would be a good idea.
 
Hmm I found something out. If you put a different boot.img in /out/target/product/warp after you did mka and tried to do it again to get it into your new cm7 build by doing mka again, it doesn't include the boot.img that is in that folder which helps me some.. though makes me wonder where it gets boot.img from in the first place

edit: made new nandroid with unmodded boot.img (last one was modded). I'll have to test it tomorrow (im staying up later than I should be atm) Hopefully with any luck this one should boot if not then its kernel time :p yayz
 
Did a little preliminary investigating on the kernel aspect. Got the kernel config file from my phone's kernel and the kernel file listed in ./out/target/product/warp (from the CM7 build output) and they appear to be the same. Ran a diff on the 2 config files and no lines were flagged as being different. Interesting...
 
You must log in or register to reply here.
Back
Top Bottom