Hey guys, I was trying to port a ROM called the Nexus Beam 5.0.0 from the Nexus S. Its an ICS CM9 based ROM. However, when I installed it, i got a bootloop, so I decided to copy the libandroid_runtime.so, libandroid_servers.so, libmedia_jni.so from the Ported ROM to the base ROM. Now it doesn't even get past the Team Kick Ass bootimage. (I used your kernel Erik XD) Do you have any ideas what could be wrong?
Why would you port it when we already have a ported one?
If you can access the recovery flash this:
http://forum.xda-developers.com/showthread.php?t=1794413
If not then flash back to stock:
http://forum.xda-developers.com/showthread.php?t=1358498
I also don't suggest following any porting guides because they are sometimes incorrect and sometimes mislead you. I learned that, now I'm waiting for XDA-University to go online. Also don't ask people on how to port stuff, they'll just reply with google this, learn by yourself, typically they're not going to give you a clue on how to start on the right foot. I bet XDA-University will fix that
You should check what the bootloop is about with adb logcat
Related
I have built a Froyo ROM from source. I got the Captivate vendor files from Krylon360 over at Cyanogen, updated them, and built a ROM. I was able to get the leaked Froyo Captivate system.img and extract it so I could get the files required for our device. The ROM build cleanly and I was able to restore it to my device but since I have an Eclair kernel it will not boot. I actually read later in a forum that an Eclair kernel won't boot a Froyo system.
Anyway, I am looking for anyone who has a Captivate with the leaked Froyo build installed to try and restore my ROM. It will not brick your phone, I promise. I took a Nandroid backup before restoring and when I saw why it wasn't booting in logcat I booted into recovery and restored my last backup.
I just want to see if this guy will boot properly with a Froyo kernel and also see if I have all the device drivers working, etc.
Thanks!
Why would you go to all the trouble to build a Froyo ROM and then not flash Froyo to your phone and try it yourself?
You flashed it your phone with the 2.1 kernel, so why not install the leaked 2.2 and then flash your custom ROM.
Seems odd you are asking others to try what you will not.
Umm Odin is required to flash the leaked Froyo.
Odin requires Windows.
I am not and never have been a Windows user. I have no way to flash the leaked Froyo to my Captivate, otherwise I would.
Does that answer your question?
It does!
Thanks.
I've been busting my butt to create a stock ROM so that we Captivate users can get rid of AT&T's stupid add-ons. Everyone jumps up and down saying, when will Cyanogen come to the phone.. I actually started working on it... and spending more time than I should.. And I think I have something that will work.
I just need people to help me validate it. And remember, I did try flashing my phone with it so there is no unwillingness on my end.
you're better off with responses with this in the dev section of the forum.. and just post the link for everyone with a big RED SIGN WARNING SAYING DEVS ONLY.
I guess I'll give it a shot. Send me a PM or a link to your files and I'll try it out. I've bricked, unbricked, rebricked, and unbricked again, so I'm pretty confident in my skills lol.
Let me set it up on dropbox real fast. I will put the URL here soon.
Sounds good.
http://dl.dropbox.com/u/6995251/full_captivate.tgz
You should only need system.img. So basically, edit nandroid.md5 and strip out the checksums for the other two files. Then copy nandroid.md5 and system.img to your recovery directory. Mine is /sdcard/clockworkmod/backup.
Report back what you find.
great work gdanke, and looking forward to what vunut has to report back with. i'd vol myself but i've only flashed my phone twice and still feeling pretty awkward with it lol.
Pvster said:
great work gdanke, and looking forward to what vunut has to report back with. i'd vol myself but i've only flashed my phone twice and still feeling pretty awkward with it lol.
Click to expand...
Click to collapse
Had to hold off flashing for now, tried it real quick and got stuck at the white att screen, so flashed back to my normal setup. Follow the thread in the development section.
Sent from my back pocket, swyped with my left butt, cheek using XDA app.
I want to try to port AOSP to my Samsung Infuse, but I need a little help. I heard that in order to port ROMs like this, you basically start by getting the source, building it, then putting it on your phone. Then try to boot into it and see what's broken and fix it(I realize fixing what's broken is going to be where majority of the work will be at.).
I downloaded the source to AOSP from Google and was able to build it, then I tried putting it on my phone but I'm unable to boot into it. How do you figure out why it won't boot? I tried running logcat on my computer when booting but it just says waiting for device and nothing else ever comes up.
Any help regarding helping me get it booting or any other general porting advice would be greatly appreciated!
Hey guys i`ve recently managed to get an SGS 4G Vibrant ( i believe that i am at right place to seek for help ) , i have the T-Mobile version of the phone. I need help switching to different/better ROM, at this moment the phone uses the stock one ( or i believe so ). I`ve been tru the threads and saw that there are a lot of stuff posted about what you need to do/have to flash a rom, but i just cant understand the right order of doing the things.
If its posible can someone really quick just post the steps for the guide for flashing a ROM to the phone. I have previous expiriance with android phone and i am aware how thing go, just as i said i cant get the right order of puting all the thing at one place.
For the phone i used to have was like, first i had to install an stocklike ROM which had recovery, but before that i had to get some kind of software for LG that alowes to flash the rom via download mode. So is the same here? It would be awesome if someone can link or atleast type all the software and other thing i need to have installed to make this work. For now what i have is the USB drivers for Samsung.
Thanks in advance!
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
sent from me
Ok, that helped, not sure how i missed it. I am gonna write down what i did so far, so you could see if i messed up something.
I rooted the phone via SuperOneClick 2.2, then i installed the SGS Kernel Flasher, and then flashed the kernel, my current phone was running an 2.3.7 android, so i used the Basic with a Twist`s kernel ( i hope i did it right ), and now the phone rebooted and some different boot screen apiared with some Robotic Chick speeking some stuff, BUT for now the phone load to there, it doesnt wannt to load.
So did i messed up something, or ....
Can you go into recovery by holding Volume Up+Volume Down while pressing the power button and as soon as the SGS 4G splash appears leaving the power button ?
If so and you can see CWM Ver. 5.0... then kernel was successfully flashed.
You shouldn't be getting a bootloop.
What ROM do you want to flash ? If you want to flash GB then I suggest Barebone/Valhalla of some kind.
If you want ICS - Go to the CM 9.1 thread and follow the instructions. After that you may change to AOKP or MIUI or all the rest of the ICS ROMs you wanna try.
invictos said:
SGS 4G Vibrant
Click to expand...
Click to collapse
This section is not for the Vibrant.
Check here: http://forum.xda-developers.com/forumdisplay.php?f=708
I am sorry I do not know how to get you back to where you started before flashing the wrong ROM.
Good luck
Well, it wasnt a bootloop, it just loaded to some point and stoped. Gladly still got the download mode and brought it back to normal to how it was. Thats why i came here to ask, `couse there are too much similiar sgs`s and stuff for them here, i just got confused whats what. Got to start from scratch anyway, at least i didnt bricked it
http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1 <---- That's a post by Lumin 30 with a guide on how to get from stock to custom GB. If you want to get to ICS then use CWM 5.0.x.x.
Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
dblackburn965 said:
Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
Click to expand...
Click to collapse
Good luck, did WiFi work out for you?
ok. i am most likely asking this in the wrong back alley for this particular set of questions, if so please inform me to stfu, n ask <insert correct forum here> and ill then be on my way.
so, i have three of the same fairly dated, samsung galaxy s (4g) / us.cellular [not hooked up] not the point.. up until this post, many attempts to create a custom recovery for this has proven useless.. my question is this, if samsung has provided the "source code" for this particular model, shouldnt the i guess, particular informaton required for building of a custom recovery should be avalible, correct?
hell, i am most likely wrong but i am curious to know..
-deadseth
"i die alot"
Follow this thread from the post I linked to, I explained to another forum member how to compile a custom boot image, which will in turn allow you to edit the recovery before you compile. This will compile a KitKat kernel, which should technically work with other KitKat ROMs but will not work with anything older.
http://forum.xda-developers.com/showthread.php?p=57558013#post57558013
well
the phone is working off gingerbread.
deadseth said:
the phone is working off gingerbread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1828171
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Good luck.
this phone has no current custom recovery yet for it, that is what i am trying to work on here.
here is samsung's open source release of the phone's os
opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=r930
These are the forums for the SGH-T959V and SGH-T959W. The link to the open source release you posted is for the SCH-930.
If you really ARE looking for SGH-T959V information read on.
We have several versions of CWM available, as well as a few TWRP versions. They are all integrated into a bootimage. They aren't built for a separate recovery partition.
Anyway in this commit, bhundven imported the samsung open source kernel files.
https://github.com/bhundven/blastof...mmit/03b6581e79545d2e40e41d0f4bedf165bb39b183
Then several people added more commits to the kernel samsung. You can read the commit history yourself:
https://github.com/bhundven/blastoff_kernel_samsung_galaxys4g/commits/gingerbread