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

Root [On Hold] JellyBean CM10.1

If you guys get this working you should make the system partition as small as possible, so we can use as much of our 4 GB as possible ;-)
 
KoRnKloWn said:
If you guys get this working you should make the system partition as small as possible, so we can use as much of our 4 GB as possible ;-)
Click to expand...

are we able to swap internal with external kinda like they do with the note 2 and other samsung devices?

oh... and just got this phone... so will be hangin around this side of the forums for a bit...
 
Hey guys, I need a system dump. If you have a rooted device, just install adb and issue the command:
[HIGH]adb pull /system[/HIGH]
zip the file and upload it somewhere it can be DL'd.
 
davidmargolin said:
are we able to swap internal with external kinda like they do with the note 2 and other samsung devices?

oh... and just got this phone... so will be hangin around this side of the forums for a bit...
Click to expand...

Not sure what you mean, if you mean disabling the system apps and setting other apps as default then yeah, but it doesn't give you any more space. We should have every app in data/apps and have the system partition totally dedicated to the rom. Things like maps, folder, browser, etc., etc., should be in data/apps so they can be replaced at will without using extra space.
 
I did a bunch of work this weekend on this and I've figured out all the problems I was having. We have all the libs and stuff copying properly, which is great!...There's only one problem.

Code: 
Install system fs image: /home/james/android/out/target/product/iconvmu/system.img
/home/james/android/out/target/product/iconvmu/system.img+ maxsize=428212224 blocksize=135168 total=363367488 reserve=4325376
Package target files: /home/james/android/out/target/product/iconvmu/obj/PACKAGING/target_files_intermediates/cm_iconvmu-target_files-eng.james.zip
Package OTA: /home/james/android/out/target/product/iconvmu/cm_iconvmu-ota-eng.james.zip
./build/tools/releasetools/ota_from_target_files -v \
       -p /home/james/android/out/host/linux-x86 \
       -k build/target/product/security/testkey \
       --backup=true \
       --override_device=iconvmu,victory \
       /home/james/android/out/target/product/iconvmu/obj/PACKAGING/target_files_intermediates/cm_iconvmu-target_files-eng.james.zip /home/james/android/out/target/product/iconvmu/cm_iconvmu-ota-eng.james.zip
unzipping target target-files...
  running:  unzip -o -q /home/james/android/out/target/product/iconvmu/obj/PACKAGING/target_files_intermediates/cm_iconvmu-target_files-eng.james.zip -d /tmp/targetfiles-zAfZPe
Traceback (most recent call last):
  File "./build/tools/releasetools/ota_from_target_files", line 865, in <module>
    main(sys.argv[1:])
  File "./build/tools/releasetools/ota_from_target_files", line 817, in main
    OPTIONS.info_dict = common.LoadInfoDict(input_zip)
  File "/home/james/android/build/tools/releasetools/common.py", line 146, in LoadInfoDict
    d["build.prop"] = LoadBuildProp(zip)
  File "/home/james/android/build/tools/releasetools/common.py", line 160, in LoadBuildProp
    name, value = line.split("=", 1)
ValueError: need more than 1 value to unpack
make: *** [/home/james/android/out/target/product/iconvmu/cm_iconvmu-ota-eng.james.zip] Error 1

It can't pack everything up. I don't know why. If anyone has any insight, that would be great, as this is the last step before I can get a flashable zip that SHOULD WORK! And I mean it!
 
In 20 minutes from the time of this post, navigate from this directory and find the CM-10 unofficial for today's date. Flash it and report your findings.

Bookmark that link. You will want it again.

Oh, and need I mention that the file "Reverb-Destroyer" should not be flashed? Yeah, I'm talking to you Risky Advent Uretime.
 
martinez41613 said:
just tested it. it didn't install. status 7 (no script) error. I'm about to modify the install script to fix it.
Click to expand...

There is a script. And it's really, really close to being right. So close, in fact, that I think the only possible problem could be failed assert. If you figure it out let me know so I can fix the build.
 
Jimmy422 said:
Just curious, what did you change from my work?
Click to expand...

I pretty much started from scratch, got it all setup, lost a bunch of time and work thanks to Microsoft, then started again:
https://github.com/xInterlopeRx/android_device_samsung_iconvmu

The vendor files are there too, but they are gonna need a lot more work. This device is odd. The specs on it cal for an msm86XX chip, but it's actually an msm7X30 with a modem from another chip for LTE I suppose. The bad thing about that is the kernel is kinda hard to find commits for, the good thing is CM has a lot of support built in for 7X30 devices.
 
xInterlopeRx said:
There is a script. And it's really, really close to being right. So close, in fact, that I think the only possible problem could be failed assert. If you figure it out let me know so I can fix the build.
Click to expand...

the good news is that updater-script isn't the problem, update-binary is. I replaced it with one I have on my laptop and the Rom installed. the bad news is that after I rebooted it, I was greeted with a black screen after the yellow triangle. but wait it there's more, while I was replacing the updater-binary, I couldn't successfully replace it because there are files with the same file name (ex: 2621a & 2621A) in system/etc/terminfo/ (since Windows isn't case sensitive) so I removed one of each. that may or may not be the reason why the Rom didn't boot.
 
martinez41613 said:
the good news is that updater-script isn't the problem, update-binary is. I replaced it with one I have on my laptop and the Rom installed. the bad news is that after I rebooted it, I was greeted with a black screen after the yellow triangle. but wait it there's more, while I was replacing the updater-binary, I couldn't successfully replace it because there are files with the same file name (ex: 2621a & 2621A) in system/etc/terminfo/ (since Windows isn't case sensitive) so I removed one of each. that may or may not be the reason why the Rom didn't boot.
Click to expand...

Thats odd. The source creates the update-binary every time it builds, so it's not like it's stale. The rom did not not boot because of the missing files in term, thats Terminal emulator. But, without last_kmsg or/and logcat I have no real idea why it's not booting.
 
xInterlopeRx said:
Thats odd. The source creates the update-binary every time it builds, so it's not like it's stale. The rom did not not boot because of the missing files in term, thats Terminal emulator. But, without last_kmsg or/and logcat I have no real idea why it's not booting.
Click to expand...

Is there a way to retrieve last_kmsg or a logcat without having the rom to fully boot?
 
martinez41613 said:
Is there a way to reteive last_kmsg or a logcat without having the rom to fully boot?
Click to expand...

if the kernel attaches right and the ramdisk gets loaded into memory and ADB starts, then things begin to fail you can use adb logcat while it's bootlooping. If you don't at least see the bootanimation it's not likely to have ADB but it's possible. If it does that, you can reboot into recovery and try to get the last_kmsg then.
 
xInterlopeRx said:
if the kernel attaches right and the ramdisk gets loaded into memory and ADB starts, then things begin to fail you can use adb logcat while it's bootlooping. If you don't at least see the bootanimation it's not likely to have ADB but it's possible. If it does that, you can reboot into recovery and try to get the last_kmsg then.
Click to expand...

Unfortunately, it doesn't display the bootnanimation. Could you reupload that file but with this update-binary?
 

Attachments

xInterlopeRx said:
if the kernel attaches right and the ramdisk gets loaded into memory and ADB starts, then things begin to fail you can use adb logcat while it's bootlooping. If you don't at least see the bootanimation it's not likely to have ADB but it's possible. If it does that, you can reboot into recovery and try to get the last_kmsg then.
Click to expand...
Hi, I got a couple errors when I tried flashing it. First, it said that EMMC and ext4 were incompatible (in recovery.log), so I decided to try using a different update-binary. When I flashed it again, it said format was supposed to have 4 args, but it had 5, so I checked the updater-script and removing "/system" from the end of the format line fixed it. Now there aren't any errors, but I'm getting the same black screen problem as martinez. It doesn't look like the rom starts at all, it's just a black screen. ADB doesn't work. I checked /proc for last_kmsg, but it wasn't there, so I'm guessing that means it's not a problem with the kernel.

Also, I tried porting a cm9 rom from the galaxy s+ (which has the same screen resolution and I think it has a similar cpu) a few weeks ago, and the same thing happened.

PS I did this in linux, so there weren't any problems with case sensitivity
 
blue_cat said:
Hi, I got a couple errors when I tried flashing it. First, it said that EMMC and ext4 were incompatible (in recovery.log), so I decided to try using a different update-binary. When I flashed it again, it said format was supposed to have 4 args, but it had 5, so I checked the updater-script and removing "/system" from the end of the format line fixed it. Now there aren't any errors, but I'm getting the same black screen problem as martinez. It doesn't look like the rom starts at all, it's just a black screen. ADB doesn't work. I checked /proc for last_kmsg, but it wasn't there, so I'm guessing that means it's not a problem with the kernel.

Also, I tried porting a cm9 rom from the galaxy s+ (which has the same screen resolution and I think it has a similar cpu) a few weeks ago, and the same thing happened.

PS I did this in linux, so there weren't any problems with case sensitivity
Click to expand...

Could you try again with my update-binary (which supports 5 agruments) and the untouched updater-script. I'm not expecting it to work but who knows, it just might.
 
You must log in or register to reply here.
Back
Top Bottom