ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
Related
Better Than LIfe
Future Echoes
7-15-11
Update #2 fr the day
Ok, stumbled across something today while trying to work some bugs.....
I managed to "inject" a recovery into the rom, and while it actually booted into recovery, and did recovery things, it even went so far as to boot the tab.
But that was it, didnt get a full boot.
So, I stumbled upon a Clockwork Recovery buy doing the right tricks i suppose, however alot needs to be ironed out. and this gets top priority this weekend, why? well ****, think about it, CWM for the CDMA Tabs for Gingerbread, and before Verizon releases GB, so this.......is great news.
Hope to have this done by end of weekend, and in doing so it might iron out the zip flash issue which means I can pump out those 2 roms.
Just wanted to share.
First, I'm removing the download link.
Second, yes I do get your PM's, and yes I do read them, and Yes, I agree....I am bad at getting back to people sometimes. Very busy trying to get GB out for the CDMA Tabs in a working fashion. I am sorry. Those of you who know me, just call, it does hurt my hands to type.
The Update.
I am yanking the download link as it is apparent that the release was/is a failure, how I managed to get it on my tab, no clue, however I cant duplicate it again.
I am working on the build, 1 for Sprint, 1 for VZW. I am trying to get it deodexed 100%, and at the same time get a VZW 3G build working.
However what is very important, that will take less time for me to flash a build to test.....is a recovery. We need a Gingerbread recovery. We do.
So I am doing a few things.....
1. doing my research on compiling a new kernal, and CWM for our tabs
2. asked for an recieved help in a new kernal and recovery
3. changing how i build these roms, no more "kitchens" or stupid "gui" based apps on Linux or Windslows that foul up the permissions, I am going 100% command line for a more effective result, and less need for revisions.
4. Working non stop through the weekend once my wife comes home from work today, so from noon today, to 3am sunday/monday I will be hard at work on all Better Than Life Releases.
I appreciate your patience in this botched release, next time, ill release a test build to a few people for a backup verification it will go without problem.
Until then, i gotta get to work.
Jim
Update..........7-12 6am
I just spent 5 hours trying every trick in the book... from extracting factory.rfs and trying to rebuild it to forcing a fake recovery... I got nothing. The problem is that ALL of the kernels that exist with CWM are ext4 froyo kernels, but the new kernel source for GB doesn't contain ext4 code... therefore, no flashy (unless by a fluke) because on reboot it tries to mount everything as rfs but it's in ext4 after you flash in an ext4 conversion kernel. I would have to design a new GB kernel with CWM and EXT4 modules in the source or revert a froyo kernel to pre-ext4 and put in a new cwm... either would take a couple of days... but I'm swamped right now. The only choice is for you to set it back up on your device like you had it and then pull a roto. Did what I could, sorry.
Click to expand...
Click to collapse
So, we tried (spacemoose and I) to get the extracted rom from my device to install on several others and ran across the same problems everyone else was having. however, the extracted rom being deodexed and zipalilgned, my device not.
So today I am going to try to get the 3G working, make the mods to the rom, and extract it, then try to inject the deodexed system and framework back in (which is always a ***** on a live device) and ill have no choice for now but to release a Heimdall flashable version of the rom.
I am waiting for that VZW release because with the sprint in my hands, and with a VZW version, all thats lacking is a Sprint tab to start making GB roms for both devices, however today will be a different story.
Oh, I did get TW4.0 to slightly work on the tab, itll either be released later, or maybe in an alpha build. I found it....well interesting. I tried it on the Psirens Rom (I have a TouchWiz4 version of Psirens) but it was way to damn buggy to release.
Ill keep yall posted today. Painpill time
Verizon wants to take their time, fine, screw them.
Gingerbread 2.3.4
Based on the Sprint update
Deodexed
Zipaligned
a little de-bloating
added CDMA/3G Verizon (3G with Verizon right now is a 50/50 shot
Kernal included in flashable zip
Just drop on SD Card, wipe everything
flash
enjoy
I am running this on my daily driver Verizon, to test and work bugs out and get 3G fully working, so expect alot...ALOT of updates and new versions of Gingerbread for Verizon.
This will be a constant updating project. So please expect bugs, and this is a last minute slap together thing tonight.
Enjoy.
More to come
Link
PULLED LINK FOR NOW 7-15-11
Omg thanks
Is this any faster/snappier than the stock SprintGB? I just finished getting it working on my vzw tab and it took me a while to get set up. Is it worth switching?
And btw thank you for all the work you do for the CDMA community, we greatly appreciate it!!
juanv145 said:
Is this any faster/snappier than the stock SprintGB? I just finished getting it working on my vzw tab and it took me a while to get set up. Is it worth switching?
Click to expand...
Click to collapse
Nandroid and try it out. That's what I'll be doing in a few minutes. Thanks Oldmacnut!
dammit. i just got Psirens 2.5 the way i like it. and now i wanna try this. i'm torn with overwhelmingly indecisive ennui now.
when u say 50/50 chance do u mean it may/may not work or itll only work sometimes?
damn seriously lol im trying to check the latest siren and i see this y bother with sirens lol
Macnut, this isent working at all for me. im flashing from your original psyrens mod and it wont flash at all. it said opening package....... cannot open sip,(bad) installation aborted.
wolfie083188 said:
Macnut, this isent working at all for me. im flashing from your original psyrens mod and it wont flash at all. it said opening package....... cannot open sip,(bad) installation aborted.
Click to expand...
Click to collapse
the link just updated. try re-download
indeed I'm lookin for the phone*.apk of VZW GB. is there an update of VZW?
Awesome, am giving this a try now.
Couple of questions:
1. Is this ext4?
2. Can we overclock with this kernel?
Thanks, this is huge for us suffering VZW tab owners!
When trying to install I got an error...something along the lines of, "error at line 11, can't symlink"
djf8 said:
When trying to install I got an error...something along the lines of, "error at line 11, can't symlink"
Click to expand...
Click to collapse
got the same error, it wont install for me
any solution to this? im tired of trying to get it to work. im now back to psyrens rc1 untill any update on this.
wolfie083188 said:
any solution to this? im tired of trying to get it to work. im now back to psyrens rc1 untill any update on this.
Click to expand...
Click to collapse
My "solution" was to just flash the Sprint rooted rom, which works with the VZW tab (not sure about 3g, though, I just use wifi anyway).
Would love it if we could get an ext4 and overclockable kernel working w/ GB for the VZW folks.
Going to download this today. This is almost more exciting than hcomb . I am glad someone is working on a vzm gbread rom.
Thanks Oldmacnut
Sent from my SCH-I800 using XDA App
Same here...
Sent from my ADR6400L using XDA Premium App
wolfie083188 said:
got the same error, it wont install for me
Click to expand...
Click to collapse
Same here...
Sent from my ADR6400L using XDA Premium App
Yeah, I'm sure something was just missed when oldmacnut compiled the zip for us. He'll get it worked out soon enough just hold off for now until there is word from him.
Getting the error as well. I am using the Sprint GB ROM in the meantime...
Oldmacnut can you give us more info on your custom ROM? I am assuming you have it rooted but the Sprint ROM is 190M while yours is 360M. Just wondering what kind of bloatware you removed and what if anything has been added to account for almost 2x the file size. Thanks
Here is the update that everyone has been waiting for At the moment, I'm only providing the modem, and rooted, stock, deodexed version of the ROM. There will be a cleaned up version to go along with all of this in due time, but we're currently working out some problems with it. I would like to note that despite this being the Froyo update, it is not without its own set of problems, and odds are you may never see another update outside of this from anywhere. However, the benefits of getting Froyo will outweigh the problems with it for most people, so have at it.
You will need a few things to get this, first, the downloads list here will be needed (obviously). You'll also need to have CWM setup and know how to use Odin. Heimdall will also work for those of you not on Windows, but I'm not providing any instructions for flashing using Heimdall. Also note that you will want to wipe data or perform a factory reset before booting into Froyo to avoid any problems. While you may get away with not doing it, you could end up with several problems, so my recommendation is to wipe data. Also, you can flash the ROM first, or flash the modem first, which ever you want to do. There isn't really a required order for it, as long as you do both parts.
[size=+1]Instructions[/size]
Download everything you need.
Odin
Froyo Radio
ROM+Kernel
CWM Kernel
CWM update.zip
Put the ROM zip and CWM update.zip on your SD Card
Flash the Radio via Odin in the PDA box
Enter CWM and flash the ROM+Kernel
Wipe Data in CWM before restarting your phone
Restart and enjoy Froyo
[size=+1]Downloads[/size]
Modem
ROM+Kernel
FAQ
How can I donate to you for this?
You can either click the "Donate to me" button above my avatar, or go through this link. Don't feel obligated to donate though, as Verizon should have given this to you (the users) long ago.
Can I still receive updates after flashing this?
You cannot receive updates after flashing this unless you revert back to DL17, which is the latest official software released by Verizon and Samsung.
If I can receive updates on this, how can I restore back to DL17?
I've been sending this to several people already that have had problems with their phones. If you need to revert back to DL17 for any reason, download this. You will need 7-zip or similar to extract it. Once you have the .tar.md5 file, flash it in Odin via PDA like you did for flashing the modem to get Froyo.
Can I return my phone to Verizon for warranty repair/service with this on my phone?
No. If you need any sort of help with your phone from Verizon, you will need to have the stock DL17 ROM on your phone. Anything else and you have voided your warranty and Verizon and/or Samsung will not have to do anything to help you. See the above question for a package to restore your phone to the latest stock software.
Are there any bugs in this release?
Yes there are, just as there is with any software. I do not know what the bugs are though off hand though as I have not been using this update. I also cannot say whether any of the problems you may have will ever get fixed, seeing as you can't even get a straight answer on why the update has been taking so long.
Is xxx modification/theme compatible with this?
Odds are that it isn't. All of the current themes and modifications for DL17 will not work on this package. They will all need to be updated to be able to work. Given that this is a relatively new release, this could take some time, especially given that it is the summer and people are on vacation (I'm looking at you trailblazer ). We will work though to try and get all of the mods ported from DL17 to EC03 so that you don't have to give up anything to upgrade.
Will you release a "clean ROM" based on this?
Yes, and it is already in progress. I have sent it out to a couple people already to ask for feedback and any issues. Once they say it is ok, I'll create a new thread with the cleaned up version. There is currently no ETA on when it will be released though.
Are there any other kernels I can use with this besides the one that comes with it?
At the moment, there isn't. I'm trying to get a custom kernel to work, but it has some problems. At the very least, we can customize the stock kernel some, but I do not know if a full source built kernel will ever be available.
Can I flash this if I am on the voodoo kernel?
No, if you are running the voodoo lagfix kernel, you will want to disable voodoo prior to doing anything. If you don't, you'll be in for some fun times with Odin getting your phone back in a usable state.
Can I get something included in the FAQ?
Yes you can. Just create a post with the following template, and I'll try to keep the FAQ updated. If I don't see it or add it right away, don't worry, I'll try and update it. If it has been a week or two and I still haven't responded, just send me a message with a link to what you want included. Here is the format to use:
Code:
[PLAIN][b]Question goes here?[/b][/PLAIN]
Answer goes here.
I'm getting ready to download it
When I go to flash the radio, Odin says it's an invalid image type
circa881 said:
When I go to flash the radio, Odin says it's an invalid image type
Click to expand...
Click to collapse
It should work You aren't extracting or renaming it at all are you?
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
circa881 said:
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
Click to expand...
Click to collapse
Your phone is in download mode when you're attempting to flash via Odin?
XD Now I feel like a ruh-tard. I forgot about that part
Wait, it's still saying invalid image type
I'm in shock... I'm on this forum every day and I missed this?! I'm going to install this and mess around with it. Ill post any bugs I find later this evening..
Kudos @imnuts for the effort!
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
jaizero said:
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
Does it really matter?
No... No it doesnt.. Its working perfectly by the way.. But Im sure you already knew that lol..
If jaizero got it to work, why couldn't I?
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
jaizero said:
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
It came from heaven!!!
Sent from my Mind
^ lolololol
Sent from my SCH-I400 using XDA Premium App
FROYO
i think i love you (no homo)
I successfully loaded the ROM.
It hang a bit longer than usual on the verizon logo but after that no issues.
Thanks imnuts and anyone else that worked to make this possible.
Kay, how are people getting this to work when I couldn't get the radio flashed
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
Ok I dl'd both files, I have Odin1.3 both blue n yellow CWM update.zip but what is CWM kernal?
P.S. I totally love you guys and many thanks to nuts for confirming my faith in opensource and saving my phone
Sent from my SCH-I400 using XDA Premium App
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
I just bought one! and love CM since the release of my first android phone, the Samsung Galaxy S2
There are only custom roms for the 8.4 and the 10.1 version.
There are no custom ROMs available for this device now, and i hate the slurpy/fancy samsung interface.
I am willing to pay for it, for the first nice and clean nightly CM 11 rom + CWM/TWRP recovery and working Gapps for this device.
This device is out for a while now and there are still no custom roms for.
So i hope there is somebody who can help, to get the custom roms madness for this device getting started.
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
ExoRRSmits said:
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
Click to expand...
Click to collapse
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
ik4evr2 said:
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
Click to expand...
Click to collapse
I am very much interested in this thanks!
nickster1 said:
I am very much interested in this thanks!
Click to expand...
Click to collapse
No problem at all. It will take me a day or two.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Can you make deodex please? I already have the stock debloate, but would be nice to have deodexed rom.
ik4evr2 said:
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
Click to expand...
Click to collapse
Well for now it sounds ok to me.
Is it rooted as well?
How debloated is it? Is samsung touchwiz removed?
That's what i'm hating the most. The settings app with tabs, i like the whole settings menu in cm.
And how fast can it see the light?
If its very nice, i can donate something for your good and hard work.
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Ludespeed said:
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Click to expand...
Click to collapse
No, I tried it, and unfortunately it doesn't work for the 12.2 version. The internal, as well as the external sd card both are locked, meaning you can't even update any apps, or saving any data... you get an error message 110, from Play Store.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Any luck ?
ExoRRSmits said:
Any luck ?
Click to expand...
Click to collapse
+1!
What about an overclock kernel? I debloated my Galaxy tab 12.2 already but have yet to successfully overclock it. I've been looking everywhere for an improved kernel or something to improve the performance, debloating didn't help it that much so a kernel or custom rom would be the next bet. Anyone point me in the right direction?
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Shaheer said:
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Click to expand...
Click to collapse
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
arcadia2uk said:
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
Click to expand...
Click to collapse
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Shaheer said:
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Click to expand...
Click to collapse
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
arcadia2uk said:
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
Click to expand...
Click to collapse
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Shaheer said:
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Click to expand...
Click to collapse
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
arcadia2uk said:
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
Click to expand...
Click to collapse
Hey!,
So I was really busy yesterday evening writing a 3 page essay and doing other homework so I didn't get anytime to work on the rom. My thoughts too were to start a new thread in the dev section for this.
I haven't gotten too far with the T520 port either as i'm still learning CM development. (I'm more used to touchwiz ) I have some time right now so give me a bit and i'll try to get a thread started and update the rom to get SD Card working.
EDIT: Actually, I can't proceed till someone can make sure that Google Play downloads app properly. If it doesn't then I need to work on that before anything or it's going to cause major issues.
Is anyone trying to build lineage 15.1 for this device? I have been trying unsuccessfully for two months. I have gotten as far as like 30%. I changed a few lines here and there and got it to build a kernel but, after it builds the kernel it runs into sepolicy errors. I'm making progress but I was wondering if anyone else was trying and had knowledge we might could swap? I'm not a full fledged developer but I have made progress.
You could ask for help from previous mainteiners of this device.
https://forum.xda-developers.com/ga.../rom-octos-t3532529/post75186090#post75186090 the reply on this post said he will maintain the device he was on octos team .you can ask him for help, hope he can
https://forum.xda-developers.com/member.php?u=6264948 his page
I don't think we will ever get 15.1. Last time I checked the kernel change, it's huge. Almost you need to rewrite everything... Can't use the old stuff. To be honest, it's not hard to port a rom. You can learn it to do it yourself in probably a day. But to build a kernel, it will take a team plus many months. It's not a one man's job. Most of the kernel developers here are taking a similar device as a base and port new functions or changes. Unless we can get a similar base, I don't think we will get a kernel works for 15.1.
It's not easy but I think it's possible I keep trying in my free time that I don't seem to have alot of
I have gotten it to compile to 52%. I ran into a failed parsing overlays error and I am trying to work through this error. Alot of work and time has been invested in this I'm hoping it pays off soon.
Joker1716 said:
I have gotten it to compile to 52%. I ran into a failed parsing overlays error and I am trying to work through this error. Alot of work and time has been invested in this I'm hoping it pays off soon.
Click to expand...
Click to collapse
you can do it bro :good::victory:
Still encountering errors but I've gotten it to 75% or better. Still trying
Joker1716 said:
Still encountering errors but I've gotten it to 75% or better. Still trying
Click to expand...
Click to collapse
Awesome, bro
Sent from my Samsung SM-A520W using XDA Labs
Joker1716 said:
It's not easy but I think it's possible I keep trying in my free time that I don't seem to have alot of
Click to expand...
Click to collapse
Good luck to you. What's your base?
I've gotten all the way through the build basically. But I keep getting a recovery partition size too large error. I am trying to work it out. Not very successfully but I am still trying. I have devoted all of my free time into trying to get this done. Hopefully it's worth it. Even if it builds the Ota zip, it may still not even boot. But I am dedicated to attempting to make this happen.
I finished still gotta try to flash it. About to pass out no sleep in a while.
Wouldn't flash. Changed updater script to kinda force it to flash. It flashed but will not boot and messes up the system mounting. I guess I will go back over my device files try to work on the partitions and other stuff.
Joker1716 said:
Wouldn't flash. Changed updater script to kinda force it to flash. It flashed but will not boot and messes up the system mounting. I guess I will go back over my device files try to work on the partitions and other stuff.
Click to expand...
Click to collapse
Awesome! Glad someone is doing this for us!
Don't give up bro! And try to ask for some help.
I managed to compile the recovery it's still a little iffy but it does flash and factory reset. dirty flashing works but if you factory reset first it deletes everything and does not mount to the usb to the computer. It also does not match the assert right. what i did was unzip the d2att rom.zip , delete the assert line on the META-INF/com/google/updater-script, and re-zip to get it to flash. It did flash. haven't tried with a SD card yet. So it's not where it needs to be just yet. If you plan on messing with this recovery it will flash in TWRP under install/install image the lineage recovery will not flash an image so make sure you know how to flash one in odin, and have everything ready if you plan on going back to a different recovery. The rom i built with it flashes tries to boot up led light pulses like 7 times and then goes into download mode . Making progress but I'm going to be taking a break for a few days. AYOR I assume no responsibilty for whatever you may do to your device with this file. if you dont know what you are doing dont mess with it if you do its At Your Own Risk . Enjoy.
if anyone wants to check it out here is the download link
#Recovery
https://www.androidfilehost.com/?fid=11410932744536990805
Truly appreciate the amount of time, effort, and sleeplessness you have put into and endured for this development! :angel:
Can you not use twrp?
ibuddler said:
Good luck to you. What's your base?
Click to expand...
Click to collapse
Not really sure if I understand the question. I'm using the d2att device tree. Msm8960 board, krait architecture. I built for the klte (krait, Msm8974) which is very similar so I could see how everything goes down then compare, make changes, and wait an extremely long time for the build to compile. My computer is old. I run into .jackserver problems like there's no tomorrow. I am a landscaper I cut grass. build walls, lay sod, plans flowers,trees, dig up flowers,trees, etc. That being said I am a tad out of my element but I started doing android developmental things on my s2 and have not stopped sometimes I think smoking crack would be easier but I kinda enjoy this type of stuff. Just basically saying I have no clue what I'm doing in technical terms but I can read compare and research and maybe get something accomplished
iloveoreos said:
Can you not use twrp?
Click to expand...
Click to collapse
Yeah I can use TWRP.?? I can use what I have build a new one etc. But I'm trying to build 15.1 for the d2att and lineage recovery is included in the build