yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shane87:
Ok, so after reading through this thread (twice), I decided to try building from this source. I downloaded the source from opensource.samsung.com, and unpacked it into my working directory. For the initrd, I used the teamhacksung stock Captivate initrd found on their github. I followed the instructions to a T, and called make KEPELER_ROGERS_defconfig, followed by make -j2. Unfortunately, my build aborts with errors. The specific error is located in drivers/media/video/samsung/tv20, although I can't remember exactly which file. (I am away from my dev computer) But the error is something to the effect of the left hand side of a specific assignment assignment instruction needs to be an lvalue. (Again, I can't give perfect info right now, but I will edit after I get back to my dev machine)

My question, to those who have tried to build this source, is have any of you ran into this error?

It occurs to me, as I write this, that the error I am seeing MAY be due to the toolchain that I use, namely the Linaro Android toolchain. I do quite a bit of building on the Talon kernel, and have written a few commits for it, but have never had trouble when using Linaro for Talon.

However, on two other kernels, for other Android devices, that I have messed around with building, I DID have some issues with the flags for Linaro. In both of those instances, however, it was due to a flag specified in the Makefile, something to the effect of error after so many warnings. By removing that flag, the kernels built perfectly, and both of them successfully booted as well. On both kernels, CodeSourcery 2009q3 toolchain built fine with or without the mentioned flag.

Anyway, as I have said, any information about this error, or instances of the same, or similar build errors, would be HUGELY appreciated. I will try building with CodeSourcery 2009q3 toolchain when I get back to my dev machine, and I will update this post with the results of that build, and more info on the error I am getting if the CS2009q3 toolchain exhibits the same error.

P.S. I know that the chances of me getting this source to build and BOOT successfully are pretty slim if boog and Jsmokey can't get it to work, but I have to try. To do less would be an insult to the great devs that have, I am sure, bashed their minds (figuratively, and maybe even literally, lol) to bring us such great roms and kernels.

[EDIT]Ok, so now that I am back on my dev machine, I got the kernel to build. As it turns out, the issue WAS my toolchain. Simply switching to CS 2009q3 arm-eabi-none toolchain fixed the build error. Now I just need to do some boot-testing.
[Captivate Android Development] Jsmokey:
Lol yeah you have to use that toolchain for all the official samsung source I've came across, kind of a hassle if you already have another installed but the code sourcery one will work to build almost anything once its installed and set up.

The boot part was the only major problem I hit in the whole process other than my first couple tries which turned out to be me just needing to reboot after building ICS. Maybe the init you used will work, if it does then I'll definitely be picking the project back up. The major snag seemed to be something keeping the partitions from mounting other than that I can't give much help since me and boog couldn't even get any sort of log working to check for errors.

I wish att would get the I897 gb released already though. Then we could at least have a more recent gb source to build, at least from how the leaks are making it look.

Anyways good luck getting it to boot, even getting some form of log working would be a big step to getting things up and running.
[Captivate Android Development] shane87:
Yeah, I wish att would quit dragging their feet, too. On the i896 source, I would almost gaurantee that the problem is something to do with the initrd. Either the initrd is not being packaged right, or the offset is being I.put wrong somewhere or something. I had a very similar problem trying to build a kernel for the motorola triumph. At boot, the phone woupd either boot straight to bootloader mode, or it would show the boot logo with the charge image splashed on top, then hang durring boot. In the end the problem was in the way the initrd was being packaged. Their initrd was not packaged at build time, instead being added by the AOSP tool mkbootimg. It turned out that I had to build mkbootimg from source, specifying the proper offset in thr mkbootimg source code. Once I got the offset right, it worked like a charm!
[Captivate Android Development] Yuna:
So, we have a movement?
[Captivate Android Development] :
Hold up, you got this kernel to boot, or are you talking about the Triumph?
[Captivate Android Development] shane87:
I was talking about the triumph, suggesting that it may be something similar in this kernel that is causing the issue. I have not had time to look into yet, I was at work when I made that post, and the idea hit me then, but I had no way to test it. I plan on looking into it in the next little bit.
[Captivate Android Development] shane87:
So I still haven't had time to test the kernel I built. However, I think I may be on the wrong track after doing some additional digging.

For starters, I am attempting to use unpack_bootimg.pl, a perl script hosted at android-dls.com to unpack the initram files from the precompiled stock rogers kernel, which I obtained from the rom package posted by TRusselo (spank his thanks button, he is the one who got the source, and he is the one who put together the stock rogers rom packages).

Unfortunately, the unpack script returns an error, saying that no initram was found. So, I tried to unpack the initram from the kernel I built, with the same results - no initram found. As it turns out, Samsung packs their initram using a different method than aosp android, so there SHOULDNT be any way the initram offset or packaging could mess up the boot.

However, I still think that the issue is in the initram somewhere. The commands in the initram files direct the kernel how to mount the filesystem, and also include the modules to allow the kernel to understand the filesystem. Seeing as how Jsmokey remarked that the filesystem is not getting mounted, the initram seems the most likely culprit.

I will continue to dig, and hopefuly I can test some tomorrow.

P.S. Does anyone know where I can find the files used by samsung to generate the initram for their build? Obviously the stock kernel, as installed by kies, has an initram, yet the files used to generate it are not included in the source. Also, to boog and Jsmokey, did you check the value of the initial kernel command string? It just occured to me that if the initial kernel command is incorrect, it could cause boot issues. And of course, I could be WAY off the mark too, since I don't have a HUGE amount of kernel building experience. These are just my thoughts, based on the experiences I have had in the building I have done.
[Captivate Android Development] boog:
The way I understand it, you have to unpack a stock zimage to use it's initramfs. Then in the config file you have to specify where your initramfs is eg: CONFIG_INITRAMFS_SOURCE="/path/to/initramfs"

I tried it with the stock kh2, kh3 and others.
[Captivate Android Development] Jsmokey:
That's also the way I understand it has to be done and how I have done it with previous builds I did with the froyo source. I also used the mentioned initramfs's along with all the other captivate gb leaks and they all resulted in the same outcome.

Sorry I can't be of more help but with how samsung has there kernel set up and the lack of info they've given out about it problems are extremely hard to track down.
[Captivate Android Development] shane87:
No kidding. What tool are you using to unpack the initrd from the stock kernel? I have a copy of the stock kernel as compiled by Samsung for the i896 gb build. As I noted above, however, I tried to unpack the initrd using two different scripts that are used to unpack aosp kernels, and both failed. Those same scripts work on cm kernels and motorola kernels that I have built, but they don't work on any samsung kernels.
[Captivate Android Development] Jsmokey:
There's a few that are specific to galaxy s kernels that will work, once again the problem has to do with samsung's method of packing up the zImage. Give me a few to get to my pc and I can link you to them.

ok here's the main one I use, I just quoted mtcarey's post from the old kh3 thread since it has the lines that need to be changed already pointed out for ya.

Also if you have dsixda's kitchen there's a script in the script directory you can copy to the directory that you have the kh2 zImage in and run it by navigating to the directory with terminal and running . name-of-extraction-script.sh zImage. Sorry I can't remember the name of the script that's why I put that.

Then there is one more option I know works which is exists repack/extract script which can be found on existz github. They are the last two on the page. You'll either need to symlink or copy the scripts and there corresponding folders over to bin for them to work correctly.

Out of those options the first two I gave are the easy ones to use, they require no extra options in the command to run but won't work for every galaxy s kernel. The exists script isn't terribly hard to run just read the included read me and you should be good to go.
[Android Q&A, Help & Troubleshooting] Tangentabacus:
Here's my dilema... My phone (Showcase) is having issues with the new CM7 and I wanted to see if it was possible to simply get a friend's un-rooted phone and do a direct clone of their Showcase to mine so that I have a working phone again. I'm getting super frustrated.

What would be awesome is a .tar for an ACS Showcase, but we Alaskan's are few and to find ones that mess with their phones is more difficult. So my hope is to just find someone's working phone and use theirs as a template to fix mine.
[HD2 Windows Phone 7 Development] shreedharcva:
Well I have been trying to have WP7 on my HD2 since a month, and although I have been successfull in burning this ROM and update it until 7403, I was not able to move further.

Whatever I tried it resulted in one or the other error.Both Zune and WPUdateCabsender failed.

At last I was able to successfully run the WPUCS as below.

Normally all cab files are zipped/rarred available at xb0xMods site.These files once zipped add some attribute once zipped.

So, here are the steps to successfully use update ca sender.

1. Create folder WP7 in C: drive and copy the files in update cab sender folder here.

2. Unzip/Unrar the cab files to WP7 folder

3. Open Command Prompt (in Admin Privilege).

4. Go to C:\WP7

5. Type attrib -A -S -H -R *.*

6. Stop any Virtual Device drivers like MagicISO, or Virtual PC.

7. Run WPUCS successfully.

This helped me to upgrade from 7392 directly to 7720 in one shot.

Also note that even if the command prompt says error and stops after restarting the device, the device will get into connectorscreen mode.

During this the Device actually updates the device, so do not try to remove battery or reset, wait for an hour until the process is completed.

Note: The only issue is during updating the device gets overheated, and sometimes it gets stuck in Magldr screen, only then restart/reset the device.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] zuzjano:
Hi Guyz,

I was playing around with the BsB Tweaks and after that I have set an unlock code on the phone. The unlock screen is completely different now and after inputting the unlock code nothing is happening. I am 100% im putting the correct one as i said it out loud with my bf next to me and it was just few seconds after I set it.

Not sure what to do now as I dont really want hard reset.. I have memories in that phone for the past2 years and I DO NOT want to loose everything.

Any ideas how I can get rid of the code.

Also if I click on menu it gives me the option to reset password but it is not click-able. Just the same way the UNLOCK is not click-able after putting in the correct code.

Can someone help me with that?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Mister B:
What 6.5.x ROM are you on !

What did you play around with in BSB Tweaks ?

Did you set this lock via standard WM lock ?

How many digits in your Password ?

Do you use CHT slider lockscreen rather than default ?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] zuzjano:
ENErgY ROM

I am not sure which ones, I believe there was something about the unlock screen display

Standard WM lock

6

CHT slider. Yes I believe that was it also in the BsB Tweaks or CHT Layout screen. I cant really remember.

Is there a way to sort this out without hard reset?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] zuzjano:
I just remembered that when I was setting the unlock code I didnt select how many minutes. It stayed on 0 minutes. I used it like that before as well and it was okay.. I tried removing the battery, the sim card and so on but nothing helps..

Please anyone who has a similiar issues can u help ?

Thanks
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] zuzjano:
Found this

About the CHT lockscreen:

Currently, the CHT lock screen does not support any PIN code or password protected unlocking.

Remove any unlock codes before turning on the CHT lockscreen or you will be permanently locked out of your device and you'll have to do a hard reset.

If you are using a gsensor app to automatically rotate the screen and you have it to always rotate, you should add the class "CHTLockscreen" to the exception list.

If you don't have the rotation app set rotate everything, but only a list of desired programs, then you don't have anything to worry about.

If you need to lock the CHT lockscreen externally, you can do it with this: "\Windows\CHT_Helper.exe -lock"

I am just wondering before i do the hard reset if there is anything out there that is able to fix this issue with the CHT lock screen..

Thank
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Mister B:
As far as I know no...

I think you change lock screen layout from HTC to Windows default or CHT lock screen hence style layout change but the reason for not unlocking is probably due to CHT lockscreen if you have indeed activated this, does warn you when seting CHT lockscreen not to proceed if using WM PIN lock & not to use with WM PIN lock.

Think a hard reset is going to be only way out but hang on for a while & do some research & thinking on what exactly you adjusted.

Lesson to learn here is Backups, so easy to backup with likes of SPB Backup & makes issues like this not a big problem.

I learnt the hard way too, hopefully some of your personal data will be on SD.

Good luck ...

Have you tried connecting to pc via usb/active sync just in case it accepts PIN in that scenario ! worth trying everything before a HR ...
[Samsung Epic 4G Touch] No_Nickname90:
Ok. So I've rooted using Zedomax's Kernal.

I'm not trying to make a back-up of my stock ROM, but there is an issue.

-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
[COLOR="Red"]E:failed to verify whole-file signature
E:signature verification failed[/COLOR]
Installation aborted.
[code]

I'm having some weird verification issue. I'm trying to make a back-up of my Stock ROM since that is VERY important. :p, but as you can see, I can't. Any ideas?

I've been searching, but I've seen things on where people are trying to flash a ROM and having this issue. It was solved by renaming the ROM to update.zip. As you can see, I'm not trying to flash a ROM, I'm trying to make a back-up, so that's not going to work for me.

Thanks for any help. Finally got my phone back from that guy over on mobiletechvideos, and I'm not trying to get it bricked again. Taking precautions. :cool:
[Samsung Epic 4G Touch] No_Nickname90:
FIXED (I think): So All I did was flash CWM using Odin instead of using ROM Manager, and it gave me CWM instead of the Stock Recovery. So now I was able to make a back-up.

I think I lost my Root, but since I have a back-up I don't really care anymore. I'll just flash the Kernal again and then just flash Starburst.
[Samsung Epic 4G Touch] Axilarry:
Hanging on Clockwork Mod

I did exactly what you did, and then reflashed ZedoMax's ROM, but think it did not work right. When I reboot into recovery, I get the exclamation point inside a triangle with little green android guy, and have to hold down power button long time and _then_ it reboots into clockwork mod. That’s not right, is it? It's a SGS2, Sprint, rooted, and then ran into same trouble as you: Recovery 3e requires signature verification for flashing external files, so it balked, throws error can't read file signature, hard stop. Replaced CWM with this: acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar to try to get around rebooting issue, but I am not good to go yet, am I? Do I have to go back to stock and start over?
[Samsung Epic 4G Touch] pdaddy:
Same problem. Anyone?
[Samsung Epic 4G Touch] JohnCorleone:
If you want a kernel that overclocks, I say go with Rogue Desperado. Zedomax hasn't been updated in a long time and you will get a lot more user support because most people overclocking are either using Rogue with SETCPU or repacked stock with Tegrak app. I honestly don't remember if Zedomax even has the latest version of CWM which is 5.0.2.7. If you want to play it safer, go with one of the kernels I mentioned and you wont have any issues with backups or restoring them
[Kyocera Zio M6000] steelrain210:
I rooted my phone and i installed cyanogen mod. After hitting backup current rom, my phone rebotted and it now has a black screen with white, small letters that say "fastoboot." I'm new to this and do not know what to do!
[Kyocera Zio M6000] sinisin:
If you installed CM7 on it there is your problem. Quit pushing buttons you don't know about. What phones CM7 did you put on your phone? Because there is no CM for the Zio. You need to do a lot of learning before you just do stuff bro. Go to the development section for the Zio and start reading.

Hope you have a computer to use.

Sent from where ever I was when I posted this
[Kyocera Zio M6000] steelrain210:
Yea, i clicked on the first option. I don't even remember what it said, but thanks for giving me that tip. And yea that's how i found about the rooting.
[Kyocera Zio M6000] sinisin:
I would recommend starting in the Easy Clockwork Mod Recovery thread as that is required stuff for running a rooted Zio. You have to know or learn how to use Adb/Fastboot from your computer. Im assuming you were trying to install/backup the rom on Rom Manager. Thats a nono on Zio.

Sent from where ever I was when I posted this
[Kyocera Zio M6000] steelrain210:
ok, so all of a sudden my phone is back on, but it says "Digital Roaming." Should i just get another phone? this is frustrating now.
[Kyocera Zio M6000] sinisin:
You are very vague in your entire description of what you did and what is happening now. If you have CM running on your phone I would sure like to know how, and what phone it was built for, because I am certain no one has ported CM to the Zio. You said you installed it and now it's working, this should be impossible. Are you sure you installed CyanogenMod? And if you did where did you get it from? And where does it say Digital Roaming?

Sent from where ever I was when I posted this
[Kyocera Zio M6000] steelrain210:
First I downloaded z4 root on my phone. The next thing I did was install Titanium Backup from the market. After all this was downloaded the phone was rooted and i was able to delete preloaded apps such as sprint tutorials and other stuff i didn't want. Then I downloaded ROM manager which is where I downloaded CyanogenMod and chose 7.1. I chose the first option on the list since i didn't see the sanyo zio and it worked. The last thing i did was attempt to backup the current ROM and that's where it took me to the black screen where it said fastboot. Idk what i did, but when i tried turning it on for the last time, my phone was back to normal. Usually the connection status says 3G, but now it says that i am roaming.

Does that help?
[Kyocera Zio M6000] sinisin:
Yes. First off there is virtually no support for Sprint Zios. Second off I would try to get in to your roaming settings and turn it to home only. Thirdly I would try to find out what phones ROM you have on your Zio(what phone the CM ROM was built for). Fourth and finally I'd say you are about a step or two away from bricking your phone out completely.

If you have insurance on it I would (lose it) and get a new one thru insurance. If not I would be very careful about what you do or try from here on out. I will check and see if the recovery for the Cricket Zio also works on Sprint, if it does I believe there is a Stock Rom from Sprint for the Zio here somewhere and that may just save you. May.

Sent from where ever I was when I posted this
[Kyocera Zio M6000] steelrain210:
Where do i find out which ROM i currently have installed?
[Kyocera Zio M6000] sinisin:
In "about phone" at the bottom of settings menu.

Sent from where ever I was when I posted this
[Kyocera Zio M6000] steelrain210:
Kernel version?
[Kyocera Zio M6000] sinisin:
No. But its around there. Its not going to say Zio but some other phone model. Look for Model ID. Or Model Number.

Sent from where ever I was when I posted this
[Kyocera Zio M6000] steelrain210:
The model number still says ZIO
[Kyocera Zio M6000] sinisin:
What kernel version? And what Mod Version?
[Kyocera Zio M6000] kkfelix:
I hope he figures out witch phone model he downloaded! It would be awesome if he stumbled upon what allot of people have been waiting for!
[Kyocera Zio M6000] sinisin:
Im thinking he didn't flash anything and is somehow back on original set up. He's not said it was running CM7. Just that its running. With a model id of Zio its super unlikely he successfully flashed anything. Kernel id and mod version will tell. But anything is possible.
[Kyocera Zio M6000] steelrain210:
Baseband Version: 2.200

Kernel Version: 2.6.32.9-perf

release@release-desktop #1

Build Number: 2.200SP
[Kyocera Zio M6000] sinisin:
Thats your stock Sprint ROM. Stay on it. Dont flash anything else as your phone has no ROMs or recovery. Just leave it alone.
[Kyocera Zio M6000] steelrain210:
Well one last thing im concerned about is it is still saying "Digital roaming"
[Kyocera Zio M6000] sinisin:
I would try reprogramming it. Update Radio and Prl. On Cricket we had a number to dial. Like #blah blah#. Find out if Sprint has a number like that.
[Kyocera Zio M6000] steelrain210:
Well should i just perform a master reset?
[Kyocera Zio M6000] sinisin:
I'm not going to say you should or shouldn't. You do what your comfortable with. It's your phone to brick.
[Kyocera Zio M6000] lowdown1983:
Yeah me too.

Ok here it is....I did the exact same thing you did when I first got my Zio bout a year ago except it didnt really install CM...It kinda flashed it to verizon some how. It showed the roaming triangle at the top and when I tried to make a call it sent me to verizon customer support lol. Since then Ive learned alot bout the ol droid OS. To fix i just brought it to the corporate cricket store and told them i let my teen nephew play with my phone and it wasnt placing calls. They just hooked it up and pretty much reflashed. I dont know it putting the stock ROM will fix or not cause i wasnt very knowledgeable bout fastboot when I did it and used ROM manager when i shouldnt. Worth a try...what more harm can happen? Better yet dont...just bring it in and get it re flashed.
[Kyocera Zio M6000] sinisin:
Hes on Sprint.

Sent from where ever I was when I posted this
[Kyocera Zio M6000] shahixx1101:
No data after flashing Cricket Zio M6000?

I flashed my zio m6000, and now no data. Also, all items related to Cricket are gone, and there is a new HW ID in place of "Welcome to Zio" now reads "Welcome to MSM76...". This is a Qualcomm,, ID. My girl has the same phone, but in good shape.
[Kyocera Zio M6000] sinisin:
Is her phone rooted or can it be? What imgs did you flash? Can you root and install the recovery on your phone? NOT THRU Rom Mngr!!!!

Sent from my CyanSensation4G