Hello forum,
I have recently been able to build the source of the teameos rom for our s3. For those who don't know, team-eos is a team of developers that make great, and clean ROMs for a variety of Google-Nexus and Nexus-like devices (Including the Xoom- If you own a xoom, there is no way you haven't heard of Team EOS) and the Asus Transformer and Transformer Prime.
Anyways, I guess that is enough with the background.
So I have been able to build the rom successfully using CyanogenMod's device tree for the VZ SGSIII... I am able to get an otapackage that I can flash. All is well except for when I reboot and try to boot the ROM. When I reboot, I see the Samsung logo (It goes away fast now, because of the unlocked bootloader), but then I never see the "Samsung Galaxy SIII" that normally follows it. Instead, the phone vibrates once after a bit, and then reboots. It keeps doing that for a while but doesn't get anywhere, even after a couple reboots...
So my question is, has anyone run into something like this when building AOSP? Or does anyone have any idea what is going on?
Any help is much appreciated.
Thanks in Advance
go to development forum and PM any of the developers there. most of tHE people here are clueless about that sort of thing.
DROID3R said:
go to development forum and PM any of the developers there. most of tHE people here are clueless about that sort of thing.
Click to expand...
Click to collapse
Ok thanks! I appreciate the heads up. I'll do just that and see what happens.
can you still get in recovery just fine?
i am assuming so?
Related
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!
I was wondering why we've never seen a TWRP build from TeamWin for the TF101. I remember when the tablet came out that a few team members had the device and there was talk of builds upcoming for our device. Then there was the long break and TWRP2 and everything that happened at TeamWin, finally with 2.1 builds showing up. But there was nothing for our device, while the TF201 and TF301 were getting love.
I pinged dees_troy on twitter and found out some interesting info:
The Recovery Partition is only 5MB on the TF101
The Kernel needs to be less than 3MB to leave enough room for TWRP, meaning a custom recovery kernel.
Without a device in a devs hands, we'll not see TWRP
https://twitter.com/Dees_Troy/status/216631211366424576
https://twitter.com/Dees_Troy/status/216631556863836160
If I didn't rely on mine daily, I'd send it over for some builds, but that is not feasible for me.
Maybe we can get a developer to notice and build this, because I'd love to see a refined touch recovery like TWRP. I mean with the kernel though, how big is it with a stripped down version of it?
Darn shame about the partition sizes, those can be moved around.. but that's not a really great fix. I'd compile it and do a tad of bug-fixing since it should be the same process, but I really don't want to mess with partition sizing being too small and stripping recovery down. X.x
I've asked before and pm'ed about being a tester, and if it happens I'll be on top of it!
See, that's one thing Moto did good with their phones. I would have no issues with partitioning being similar, but I think they did go a little over board on what the system got versus what the consumer should be able to use for storage, IMO.
If there was a guide and I knew I could do it without creating to much headache trying to get it right, then I'd start on a similar project. My biggest problem is, I don't know very much about this at all. The last time I did any programming, I was in highschool and was learning C++ and did some PHP coding, but that doesn't apply here. HaHa.
TWRP has a step by step compile from source linux guide
Just the partitioning, I think it would work straight from source pretty well, but considering that the partition is too small that's where it gets tricky
Thing O Doom said:
TWRP has a step by step compile from source linux guide
Just the partitioning, I think it would work straight from source pretty well, but considering that the partition is too small that's where it gets tricky
Click to expand...
Click to collapse
just build it and see what the size is then we might be able to engage one of the kernel devs to help strip stuff out
Sent from my CM9 Transformer TF101 using Forum Runner
Alright, I'll compile from source and see what I can do. Give me a while though, because I'm upgrading my computer.
Sent from my TF101
Thing O Doom said:
Alright, I'll compile from source and see what I can do. Give me a while though, because I'm upgrading my computer.
Sent from my TF101
Click to expand...
Click to collapse
just checking in, any progress?
Sent from my CM9 Epic 4g Touch using Forum Runner
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Thing O Doom said:
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Click to expand...
Click to collapse
no worries, appreciate the effort
Im also eagerly awaiting any news on this... Im stuck on Rogue recovery because all the other versions dont use the MicroSD card, only the internal memory
Can someone post where I can find the partition layout/structure/description? (or PM it to me, that woul work as well)
Thing O Doom said:
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Click to expand...
Click to collapse
Hammerfest said:
Im also eagerly awaiting any news on this... Im stuck on Rogue recovery because all the other versions dont use the MicroSD card, only the internal memory
Can someone post where I can find the partition layout/structure/description? (or PM it to me, that woul work as well)
Click to expand...
Click to collapse
Looks like rayman has taken the reins on this one. There is a thread in dev for a WIP TWRP recovery
Yep he mentioned it and took over, which is great! Works decently well.
Hello all,
I'm looking for a Dev phone, something that can be broke for a couple of days while I'm trying to create custom roms/firmwares etc, and something that won't leave me without a phone if I brick it. If anyone is willing to donate a SCH-R740 to a rookie developer I will do my best to get CyanogenMod 9 and 10 ported to this device, as well as maybe a few custom firmwares.
I won't make promises, but I've been having some success, I've successfully ported CWM with pre-built kernel to the device, so there is a bit of a glimmer of hope.
If your willing to donate a phone to this my project please send me a private message.
CowboyEnvy
I have do have one. Its soft bricked. Stuck on the boot screen
trinidys_zte_Mt_n8000_rooted_stock mod stripped rom
Cool, before you agree to donate if you can get to bootloader you should be able to derrick via odin flash
Sent from my SCH-R740C using xda app-developers app
trinlu27 said:
I have do have one. Its soft bricked. Stuck on the boot screen
trinidys_zte_Mt_n8000_rooted_stock mod stripped rom
Click to expand...
Click to collapse
Sorry, just re-read my reply, I'd be more than happy to accept a softbricked phone as a donation as a dev phone, I would like to let you know however, that since you can get into the boot loader there are enough resources currently available that you should be able to de-brick the phone yourself if you wished to press it back into service...
The current ongoing development thread, and Stock ROM images are available at:
http://forum.xda-developers.com/showthread.php?p=49921529
looking for SCH-R740C dev phone
Still need a Dev phone, wanting a device, I can try Odin flashes on w/o risking my personal use phone.
CowboyEnvy
dev phone sch-R740c Cricket
cowboyenvy said:
Still need a Dev phone, wanting a device, I can try Odin flashes on w/o risking my personal use phone.
CowboyEnvy
Click to expand...
Click to collapse
Hello CowboyEnvy:
Not sure if you still need this model phone for a donation but I happen to have one that is already rooted with ckockwork mod and super su installed. Just has a stock rom with a little trimming on the programs that originally came with it. All I can say is that you pay the cost to get it to you and its yours, otherwise, being homeless and no work, the best I can offer you.
Thread closed, XDA is not a place to "beg" for Dev Phones...
Hi, guys and gals!
I'm new to the forums, I had a question to ask and I apologize now if this might be too broad or maybe just a stupid question(s).
So, I have a ASUS transformer infinity, the Tf700t tablet which is on the 10.6.1.14.4-20130329
And i've been looking around to figure how why the hell this thing is so slow!, And over researching everyone seems to ultimately point to downloading custom roms like updating the tablet with these i guess jailbreaking methods.
A couple months ago I managed to unlock my device (when I load up the tablet, when it says ASUS on the top left if says this device is unlocked).
Now my question is, I found this CROMI-X, forum on this website that tells you how upgrade the device, and it keeps telling me to root my device, which I can't seem to find anywhere the most recent on for the build that i am on (10.6.1.14.4), also I've downloaded TWRP and i was suppost to make a recovery img or something a ".blob" and it was asking me to write down the exact name of my tablet and I can't seem to find where that is, and i guess you can say I got cold feet to accept since it said that my device can get bricked, SO my question would be, is there any kind of guide out there with the latest updates i'm assuming kitkat? for noobies like me or maybe a video tutorial on how to do all this.
Cause i literally only have my device unlocked, I don't think i've actually rooted my device.
But yea that's about it, sorry if im asking for too much i thought this would be my only hope on making this tablet worth my while, cause this thing wont stop lagging (i've tried cold booting and restoring this thing like 10 times nothing seems to be doing the trick).
Thanks again
duperdavid said:
Hi, guys and gals!
I'm new to the forums, I had a question to ask and I apologize now if this might be too broad or maybe just a stupid question(s).
So, I have a ASUS transformer infinity, the Tf700t tablet which is on the 10.6.1.14.4-20130329
And i've been looking around to figure how why the hell this thing is so slow!, And over researching everyone seems to ultimately point to downloading custom roms like updating the tablet with these i guess jailbreaking methods.
A couple months ago I managed to unlock my device (when I load up the tablet, when it says ASUS on the top left if says this device is unlocked).
Now my question is, I found this CROMI-X, forum on this website that tells you how upgrade the device, and it keeps telling me to root my device, which I can't seem to find anywhere the most recent on for the build that i am on (10.6.1.14.4), also I've downloaded TWRP and i was suppost to make a recovery img or something a ".blob" and it was asking me to write down the exact name of my tablet and I can't seem to find where that is, and i guess you can say I got cold feet to accept since it said that my device can get bricked, SO my question would be, is there any kind of guide out there with the latest updates i'm assuming kitkat? for noobies like me or maybe a video tutorial on how to do all this.
Cause i literally only have my device unlocked, I don't think i've actually rooted my device.
But yea that's about it, sorry if im asking for too much i thought this would be my only hope on making this tablet worth my while, cause this thing wont stop lagging (i've tried cold booting and restoring this thing like 10 times nothing seems to be doing the trick).
Thanks again
Click to expand...
Click to collapse
Hey there I can help you get this taken care of why dont we move to email
Shoot me an email at [email protected] and we can get you on your way :good:
lj50036 said:
Hey there I can help you get this taken care of why dont we move to email
Shoot me an email at [email protected] and we can get you on your way :good:
Click to expand...
Click to collapse
Just send you a email, thanks again for taking the time to help me out I really appreciate it!
lj50036 said:
Hey there I can help you get this taken care of why dont we move to email
Shoot me an email at [email protected] and we can get you on your way :good:
Click to expand...
Click to collapse
Maybe other users may be benefit if the information is here, don't you think? :silly::laugh:
LetMeKnow said:
Maybe other users may be benefit if the information is here, don't you think? :silly::laugh:
Click to expand...
Click to collapse
I always try to get the user to post what fixed it in the end.:angel:
But now we have moved to team viewer.....
I give better support than asus.... :good:
lj50036 said:
I always try to get the user to post what fixed it in the end.:angel:
But now we have moved to team viewer.....
I give better support that asus.... :good:
Click to expand...
Click to collapse
Everyone knows how bad the stock Asus comparing to your Crombi-kk, haha...:laugh:
@lj50036 that you find and take the time to answer questions like these is nothing short of amazing considering the work you put in for this tablet. My hat goes off to you, Sir!
I think we can mark this thread as SOLVED
The Solution
So here is what we did
@duperdavid has his tablet unlocked already....:good:
All I did was help him install fastboot, adb, and Windows drivers which can be tricky.....
We than installed TWRP with fastboot
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Than we got him a ROM and a GAPPS
Made a backup with twrp.... Than did a full wipe of internal...
Than he did not have a sd card so we pushed the rom and gapps onto the tablet while it was booted into twrp
Code:
adb push nameoffile.zip /sdcard
Than we flashed new rom & gapps
booted into Rom !!!!! Win
We backed up his Nvflash blobs also
lj50036 said:
So here is what we did
@duperdavid has his tablet unlocked already....:good:
All I did was help him install fastboot, adb, and Windows drivers which can be tricky.....
We than installed TWRP with fastboot
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Than we got him a ROM and a GAPPS
Made a backup with twrp.... Than did a full wipe of internal...
Than he did not have a sd card so we pushed the rom and gapps onto the tablet while it was booted into twrp
Code:
adb push nameoffile.zip /sdcard
Than we flashed new rom & gapps
booted into Rom !!!!! Win
We backed up his Nvflash blobs also
Click to expand...
Click to collapse
Wow, that is a lot of helps in one session....:good: I really like the Nvflash blobs parts...:laugh:
lj50036 said:
Than we got him a ROM and a GAPPS
Click to expand...
Click to collapse
I think that the Crombi-kk is the best right now, haha...:silly:
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
SedentaryDev said:
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
Click to expand...
Click to collapse
did you installed cm from here http://getcm.thebronasium.com/?device=u8833?
303
I didn't install it at all. This is just how I got the phone. I can tell you that it's CyanogenMod version 11-20141114-NIGHTLY-u8833
That could be the problem. You never know what the previous owner did or what they flashed could be a bad download, the wrong firmware, etc. Best to get back to stock and start over so you know exactly what has been done.
Hmm... probably. Right now going back to the stock ROM would be an improvement. Could I get some help with that, then? I haven't been able to find clear steps to do that with my specific phone, and when I went to Huawei's web site, I couldn't find the ROM for the Y300-151 and wasn't confident the Y300-100 was suitable.
I've used CM11, but I'm not familiar with that phone, so unfortunately I can't help with that specifically. There should be plenty of help on XDA. Just search for that specific model. Sometimes it takes a while to find what you need, but I'm sure its there. If it's done right CM11 has never let me down.
I'm sure CM11 works fine for most people, but my instincts tell me that my phone is underpowered for it. Ok, I'll look elsewhere or start a new thread about getting back to the factory ROM.
Yes, first thing to do is get back to stock. But don't give up on CM11. It should work fine on underpowered phones. It's just a slightly modified version of vanilla android which is a fairly light ROM.
I hope you figure it out.
Good luck!
If what you say is true, then I expect I'll be right back here again. I doubt that the wrong binary was used--I dunno, maybe something was wrong w/the installation procedure, but I'm sure the right binary was downloaded. In which case, maybe I should be attacking these problems directly, since I'm having trouble getting support for installing the factory ROM.