Related
I compiled aosp from source and flashed the rom on my phone through rom manager. I used the binary files from here: http://forum.xda-developers.com/showthread.php?t=1421188 and used the tweak to stop the recovery image from compiling. After flashing and upon booting I get this weird band going horizontal with the screen. I've attached a screen shot and was wondering if someone knew what I di or didn't do to cause this issue.
edit: I finally ran the exact script and pulled my prop files from an aosp rom 4.03 rom on my phone. If you're following the guide on cdma be prepared to extract the files you need or pull them from a git repose of a rom that's working on your phone. I tried the binaries posted in the cdma development section but they didn't work for me. Just some food for thought.
did you accept the agreement using the path for the source or what you did?
NICEGYPT said:
did you accept the agreement using the path for the source or what you did?
Click to expand...
Click to collapse
I'm not sure I know what you mean.
Any reason why this isn't in the Compile thread?
EddyOS said:
Any reason why this isn't in the Compile thread?
Click to expand...
Click to collapse
Is there a compile tread on XDA other than here: http://forum.xda-developers.com/showthread.php?t=1386615&page=15 ? I posted in the Q & A section because the moderator wanted people to post their questions here. I hope I can get some help with this issue either way. Thanks
I think in this case it might be worth posting in that thread, or at least link this thread in there as more people will then see the issue you've got
EddyOS said:
I think in this case it might be worth posting in that thread, or at least link this thread in there as more people will then see the issue you've got
Click to expand...
Click to collapse
Thanks.
10 char
http://www.sendspace.com/file/zdq9uo
Working:About everything
Broken:Camera works for some people.
Tweaks:What comes with flexreaper, nothing special added in this version. Next version will have build.prop tweaks and hopefully working camera.
If anyone wants to help with development of roms for the iconia a100 just PM me.
Yesterday, I downloaded both Tabooyay and flexreaper from posts found in the Rom Thread in the General section.
Just curious if the two you have posted here in Development are the same or if you have made modifications within the last 24 hours?
I haven't flashed either yet so I'm just curious. Perhaps you could give each a version number or some other identifier.
The MD5's I get are:
Taboonay_A100.zip >> d16775ad627af91e43045d5a686a976a
Flexreaper_A100.zip >> 6b463663fc008ac2cb7a802c960e195b
MD5's are your friend. First thing to tell people to check if they experience issues.
Land Master said:
Yesterday, I downloaded both Tabooyay and flexreaper from posts found in the Rom Thread in the General section.
Just curious if the two you have posted here in Development are the same or if you have made modifications within the last 24 hours?
I haven't flashed either yet so I'm just curious. Perhaps you could give each a version number or some other identifier.
The MD5's I get are:
Taboonay_A100.zip >> d16775ad627af91e43045d5a686a976a
Flexreaper_A100.zip >> 6b463663fc008ac2cb7a802c960e195b
MD5's are your friend. First thing to tell people to check if they experience issues.
Click to expand...
Click to collapse
They are both the latest version as the ones on the a500 forum
Thanks
Installed it yesterday, works great. Much appreciated.
Does the gold edition work on this ROM
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Thanks guys, broken camera is front or back or both? i am using the A500 version of Flex and the front camera is upside down even during chat and Wifi dies after inactivity (already turned it in settings to not do it)
I will try to push a full compatible build for the a100 based on the a100 ICS leak.
Give me some time and I need testers as I don't have a a100.
civato said:
I will try to push a full compatible build for the a100 based on the a100 ICS leak.
Give me some time and I need testers as I don't have a a100.
Click to expand...
Click to collapse
I am very much looking forward to your A100 release. I'm running Flexreaper now using Zeronulls boot.img. If you need me to test anything, I am willing to do so.
Gibson.Dubs said:
I am very much looking forward to your A100 release. I'm running Flexreaper now using Zeronulls boot.img. If you need me to test anything, I am willing to do so.
Click to expand...
Click to collapse
Where do I get that boot.img , because from what I hear the stock boot.img doesn't got full root ?
civato said:
Where do I get that boot.img , because from what I hear the stock boot.img doesn't got full root ?
Click to expand...
Click to collapse
The stock boot.img is usable. You may just need to re-root the rom when you flash it.
Will upload first release today
EDIT
To the OP , credit to the original rom builder would be great.
I could care less you changing build.prop , but I do care not being recognized.
It takes many hours to build a good custom rom and to mod.
Thanks , civ.
civato said:
Will upload first release today
EDIT
To the OP , credit to the original rom builder would be great.
I could care less you changing build.prop , but I do care not being recognized.
It takes many hours to build a good custom rom and to mod.
Thanks , civ.
Click to expand...
Click to collapse
Sorry about that, noone else had took any offense and I appologize for not giving you credit.
blmvxer said:
Sorry about that, noone else had took any offense and I appologize for not giving you credit.
Click to expand...
Click to collapse
No problem but understand it is all free and for the community so respect is needed.
So again please in your OP you need to refer to the base of the rom , it is even a XDA rule to point to the source.
Thanks.
as for tabooyay not care "[MOD] 2 MicroSD Internal Memory Swap".
otherwise very good ROM prometeur.
good job thanks
Thread closed.
OP was asked to give credit, none was given. If you make a new thread, do so ONLY with giving full credit as to the source of the code..
HELP - my ATT Galaxy S3 is bricked after flashing Liquidsmooth 2.8.
I mistakenly downloaded from the link in the ATT Galaxy Note forum, but apparently posting there to ask for help left some Note owners severely POed. I had downloaded V4.2.2 from the same Note thread and flashed it with no problem.
I see the same download link in this thread in the Galaxy S3 developers forum. For some reason, this thread was closed on July 1.
Before flashing 2.8, I wiped the data and cache, then flashed the ROM and it installed with no problem. But on reboot it didn't restart. Battery has been pulled several times, Vol+ - home - power does nothing at all.
I've tried the instructions here, but ODIN doesn't recognize the phone when I plug it in.
I know there's dozens of brick-related threads -- most of them seem to have the same answers in the midst of a lot of BS.
I've installed quite a few ROMs on my phones, and have never had this problem come up before.
Any help getting my phone back would be appreciated.
I have the same issues as others in several other brick threads. Battery out and phone plugged into desktop, the red LED comes on and the desktop dings but the phone doesn't show as a device.
I've tried all of the suggestions in this thread, even though it's for a Captivate. No joy with any.
I tried installing the driver downloaded from Samsung, but got the attached error. I got the same error when I plugged the phone in the first time after flashing 2.8.
Wondering if I'm going to have to send the phone to Mobile Tech Videos for a JTAG job??
Again, any advice would be appreciated. Hopefully, I don't PO any S3 owners.
You bricked it. Mail it out for jtag. Next time, only flash software intended for your device.
Don't
Flash
Roms
For
Different
Devices
.
mrhaley30705 said:
You bricked it. Mail it out for jtag. Next time, only flash software intended for your device.
Click to expand...
Click to collapse
Yeah, I was afraid of that.
I can assume the S3 Liquidsmooth thread was closed BECAUSE it offered a ROM (2.8) that doesn't work on the S3, even with the video with v2.2 on the S3 posted right at the top of the OP.
Liquidsmooth seems to be at the root cause of much grief for our phones. Maybe the good dev can pull it off the forum until these issues are resolved.
Sent from my SAMSUNG-SGH-I747 using xda premium
jamesc760 said:
Liquidsmooth seems to be at the root cause of much grief for our phones. Maybe the good dev can pull it off the forum until these issues are resolved.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Doubt will get reimbursed for all the money heading to MobileTechVideo
Icersman said:
Doubt will get reimbursed for all the money heading to MobileTechVideo
Click to expand...
Click to collapse
Of course you're not going to be reimbursed anything... NO ONE BUT YOU MADE YOU FLASH THE WRONG ROM. Why should anyone else pay for it...
Flashing any Rom is done at your own risk.
studacris said:
Of course you're not going to be reimbursed anything... NO ONE BUT YOU MADE YOU FLASH THE WRONG ROM. Why should anyone else pay for it...
Flashing any Rom is done at your own risk.
Click to expand...
Click to collapse
Lighten up Francis. I was being sarcastic.
I'm fully aware of the risk. I'm also fully aware that the v2.2 ROM in the OP for Liquidsmooth and the updated 2.8 ROM that was added to the OP supposedly worked in the S3. Hence my suspicion that the thread was closed -- BECAUSE 2.8 BRICKS S3s
I am sorry you flashed a rom that did not belong on your device. I really am sorry.
but your posting got me to thinking why I was unable to install v2.8. after using the search bar I found a similar issue. followed the threads and was able to update the bootloaders and have flashed successfully flashed liquid smooth v2.8. I was surprised to have found it since you claim the post was taken down. it must have just been moved. It did not brick my device by the way.
I have enjoyed the work the liquid smooth team has turned out since I got my s3 and will continue to support them.
aircooledbusses said:
I am sorry you flashed a rom that did not belong on your device. I really am sorry.
but your posting got me to thinking why I was unable to install v2.8. after using the search bar I found a similar issue. followed the threads and was able to update the bootloaders and have flashed successfully flashed liquid smooth v2.8. I was surprised to have found it since you claim the post was taken down. it must have just been moved. It did not brick my device by the way.
I have enjoyed the work the liquid smooth team has turned out since I got my s3 and will continue to support them.
Click to expand...
Click to collapse
I enjoyed v2.2 after flashing it a month or so ago. Here is the thread that I downloaded 2.2 from. The updated link to Goo in the OP sends you to a page that contains the download links for 2.7 and 2.8.
The final post by Forum Moderator Jayharper08 posted on 7/1 says simply "Closed per Mike's request."
I had downloaded 2.8 prior to the 1st, so I assumed that all was OK. I don't see anything anywhere about the need to update the bootloaders, so again I assumed that clearing data and cache before flashing would be sufficient.
I don't blame Mike or the LS team. I would like to continue using the ROM once I get my "brick" back from MobileVidTech. To that end, which thread did you download 2.8 from?
http://forum.xda-developers.com/showthread.php?t=2346973
aircooledbusses said:
http://forum.xda-developers.com/showthread.php?t=2346973
Click to expand...
Click to collapse
Thanks. I searched the S3 Dev forum for "liquid smooth 2.8" and the only reply was to my linked thread.
So, when my phone comes back I'll flash from this thread.
Sent from my A500 using xda app-developers app
OK, now that I've had the chance to look at aircool's reply on my desktop, I'm confoozed.
I'm not a noob, but can someone 'esplain (without trolling) why there are two forums:
AT&T Galaxy S III Original Android Development
Original development for the AT&T Samsung Galaxy S III
and
AT&T Galaxy S III Android Development
Android development for the AT&T Samsung Galaxy S III
In my less than expert opinion, they seem redundant.
Original development is for source built roms/kernel with the work done originally by the op.
Development is another project that has stemmed from those works (kangs)
Or roms/kernels based on a modified TouchWiz.
studacris said:
Original development is for source built roms/kernel with the work done originally by the op.
Development is another project that has stemmed from those works (kangs)
Or roms/kernels based on a modified TouchWiz.
Click to expand...
Click to collapse
Thanks for clarifying that -- I think I get it.
And I apologize for spouting off earlier in the thread. I was a little cranky about bricking the phone. Of course, at my age I'm usually cranky!
I use and like the cleanbean ROM, but recently I've been constantly prompted to update to a newer version of android. I want to know if this would have a bad affect on the ROM.
foxrumor said:
I use and like the cleanbean ROM, but recently I've been constantly prompted to update to a newer version of android. I want to know if this would have a bad affect on the ROM.
Click to expand...
Click to collapse
To update official software, you need to be on stock software, unrooted, with stock recovery What version of Jelly Bean is your CleanBean ROM based on?DO NOT take any updates while rooted or on custom ROMs.
Yeah don't ever take official OTAs while rooted/on a different rom other than stock. Hell i never even take an ota for the rom that I'm on, i always do things myself to ensure everything works right. Your build.prop needs to be updated to trick the OTA update, check the developer's thread to see if he posted one for you to flash
Sent from my SPH-L710 using XDA Free mobile app
sevenpioverthree said:
Yeah don't ever take official OTAs while rooted/on a different rom other than stock. Hell i never even take an ota for the rom that I'm on, i always do things myself to ensure everything works right. Your build.prop needs to be updated to trick the OTA update, check the developer's thread to see if he posted one for you to flash
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Okay the for the help.
Hello I was looking around for a solution for this myself and came across your thread. Did you happen to find one? If not I'll keep looking and could let you know if I find one. Thank you.
Mystina83 said:
Hello I was looking around for a solution for this myself and came across your thread. Did you happen to find one? If not I'll keep looking and could let you know if I find one. Thank you.
Click to expand...
Click to collapse
Please refer to this thread courtesy of CNexus: http://forum.xda-developers.com/showthread.php?t=2209418
It has all the answers to your questions regarding ota updates (he even made a guide on how to edit your build.prop yourself!)
Be careful when editing your build.prop though, I'm sure CNexus includes this in his guide but just in case, make a copy of it and store it somewhere safe like an external sd or your computer before you edit it. Good luck! Also be sure to hit that "thanks" button, i find myself thanking almost all his posts
Sent from my SPH-L710 using XDA Free mobile app
sevenpioverthree said:
Please refer to this thread courtesy of CNexus: http://forum.xda-developers.com/showthread.php?t=2209418
It has all the answers to your questions regarding ota updates (he even made a guide on how to edit your build.prop yourself!)
Be careful when editing your build.prop though, I'm sure CNexus includes this in his guide but just in case, make a copy of it and store it somewhere safe like an external sd or your computer before you edit it. Good luck! Also be sure to hit that "thanks" button, i find myself thanking almost all his posts
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Thank You Sevenpioverthree. I will definitely give it a look. Still learning a lot around here and learning one thing leads to learning another. Thanks again!
Mystina83 said:
Thank You Sevenpioverthree. I will definitely give it a look. Still learning a lot around here and learning one thing leads to learning another. Thanks again!
Click to expand...
Click to collapse
sevenpioverthree said:
Please refer to this thread courtesy of CNexus: http://forum.xda-developers.com/showthread.php?t=2209418
It has all the answers to your questions regarding ota updates (he even made a guide on how to edit your build.prop yourself!)
Be careful when editing your build.prop though, I'm sure CNexus includes this in his guide but just in case, make a copy of it and store it somewhere safe like an external sd or your computer before you edit it. Good luck! Also be sure to hit that "thanks" button, i find myself thanking almost all his posts
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Can one of you post a patched version of the cleanbean ROM with the modified file? I'm afraid to modify system files myself.
foxrumor said:
Can one of you post a patched version of the cleanbean ROM with the modified file? I'm afraid to modify system files myself.
Click to expand...
Click to collapse
I wouldn't be too afraid. Just be as careful as you can be. I believe editing the build.prop is pretty harmless so long as you keep a copy of the original somewhere. You should do it yourself! You'll feel awesome knowing you took another step and got your hands a little dirtier and have 1 less thing to have to depend on someone else for
sevenpioverthree said:
I wouldn't be too afraid. Just be as careful as you can be. I believe editing the build.prop is pretty harmless so long as you keep a copy of the original somewhere. You should do it yourself! You'll feel awesome knowing you took another step and got your hands a little dirtier and have 1 less thing to have to depend on someone else for
Click to expand...
Click to collapse
Well we don't have to warry about that any more since my phone crashed and I forgot to backup that ROM so I'm back on cm11, but no one else had a thread answering this question so I hope it helps others.
Hello fellow XDA members, I recently purchased a Le Pro 3 and a Le S3 during the flash sale and would like to use Cyanogenmod on my devices. I was wondering if anyone on this forum has ever ported a ROM before as I have not, and only know about the CM porting guide and opensource.le.com for the kernel source. If anyone has any tips or would like to assist me in porting CM13 to the Pro 3 please reply to this thread or PM me. Thanks, and let's hope LeEco releases the source soon!
Love to help but this isn't my department ????. But we should probably see more support in a couple more days once they start arriving here
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
dr4stic said:
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
Click to expand...
Click to collapse
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
limitlesscodes said:
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
Click to expand...
Click to collapse
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
dr4stic said:
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
Click to expand...
Click to collapse
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
limitlesscodes said:
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
Click to expand...
Click to collapse
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
dr4stic said:
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
Click to expand...
Click to collapse
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Not a lot. I've identified the CAF tag the sources are based on and have been working to separate the relevant LeEco mods from the less relevant ones. I've also been attempting to remove the leeco specific things from the drivers that i'm keeping since they're a horrible mess and CM won't be able to make use of them anyway. I've also been finding the appropriate open versions of the drivers and taking the latest ones instead.
The mods from LeEco seem to be a mess, the dmesg output I got from a user on the chinese model (the x720) had segfaults from the modifications just after boot. The logcats are so full of errors I was unable to get the user to send me a full logcat from boot.
Interestingly enough, the chinese system rom looks like it came from a Le Max2. This makes sense since it's LeEco's first msm8996 device, and the Le Pro3 is the second one. I imagine the kernel sources work across a number of the 8996's.
Can you send me the link to where you got the open drivers.
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Please share the sources.
Sent from my LEX727 using Tapatalk
ceo.mtcl said:
Please share the sources.
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
here
limitlesscodes said:
here
Click to expand...
Click to collapse
Thank you so much!
limitlesscodes said:
here
Click to expand...
Click to collapse
This is not a International version? Its USA version? Where is the International source code?
Here's a mega mirror in case the drive link goes down.
https://mega.nz/#!7Ek3HYaB!1H0WibOjwlg1P0vaaJ2qcrAAsl-PjruB9-_X1ECqfnw
Wish i could help more, but it looks like the kernel source is in there too, perhaps that means a fully functional cm13 rom that works AT LEAST as well as the stock rom. VERY EXCITE!
+1
I'm also waiting for CM13.
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
:good:
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
giogio1 said:
:good:
Click to expand...
Click to collapse
Waiting for CM 14.1
http://opensource.le.com