Related
Android 2.0.1-r5v0.6
Dead:
==============
After spending some time and looking over this rom and ways to make it work with out any legal issues. The most viable option was to build something like what cynanogen has built. His process takes the proprietary bits (all google apps including sync) and copies them off onto the SD card before doing a update. After the update it copies them back to the newly installed rom. This method basically does a automated backup/restore of your licensed applications. I can't do this for several reasons including that we are supposed to be coming from a 1.5 OS to a 2.0.1, which isn't compatible with the older application set.
Temporarily Offline:
==============
I am sorry to have to do this but we are now having more then just a small handful goofing with this ROM and I need to take this offline while I inspect each of the parts and make sure all licensing is in order since its a bit more then the google Opensource framework. I know that several other ROM creators have not paid much attention to it as I am going to now but I really don't want to upset any IP holders like what happened to Cynanogen a couple months back.
I will put it back up but I want to make sure that I am totally covered and don't have any issues.
version 0.6: download (offline)
==============
-fixed wifi thanks to http://forum.xda-developers.com/showthread.php?t=593620
-Now starts up with Android stock keyboard. (No longer needs HTC_IME.apk for second keyboard)
A few have asked for this ROM so I thought I would put it up here for anyone that wants to contribute to or take from it.
This ROM is only compatible with the Sprint CDMA HTC Hero. It is not finished and still requires some work but its good enough for my day to day use and I am sure others may find the same potential.
This ROM is vanilla android and what it takes to actually get it running on a CDMA phone. It is built off of this GSM variant. I am going to try and work to remove the google bits so that you can use Cynanogens method of extracting your own and then doing a follow up update to install them. My efforts for this is not to build a better rom but to build a cleaner base that has limited to no proprietary IP.
Credits to all on this forum how have helped or contributed in any way to building the roms that are here. I would point out names but there are to many to name. I am positive that anyone that pays attention to this forum will know who you are. I used many parts of these ROM's and many others on XDA to build this one.
This is my first ROM and was primarily made for myself to help me learn how to create a custom ROM.
Here is the link to my blog where I originally posted about this and a video of it booting.
Here is the Youtube video of it booting: http://www.youtube.com/watch?v=tRTh-rXKe-E
*Warning*: Don't attempt to flash this ROM onto anything else unless you know what you are doing! I am not responsible for any device malfunctions or "Bricks".
Notes on Installing:
- Run a Nandroid backup before you do anything.
- Make sure you do a full wipe first. (Sorry )
- Run the update zip found * Version 0.6 *(offline) from the recovery console.
To get the HTC keyboard installed: (Now Optional as of Version 0.6)
- Follow the instructions here.
Things that don't work:
- Gallery some times has issues.
- Camera
- Wired or Wireless Tethering (Now Testing)
- Orientation
- Trackball light
- Trackball click (Rolling and moving are fine)
- (Let me know if something else needs to go here.)
Possible issues that are not repeatable:
- speaker not working on out bound calls? I made 30 test calls to my home phone and was not able to replicate this issue. Needs to be verified (see here)
Awesome! Thanks! disregard my PM lol.. Great timing.
VoXHTC said:
Awesome! Thanks! disregard my PM lol.. Great timing.
Click to expand...
Click to collapse
LOL I was just getting to replying to you!
im trying it now nice work
Let me know if any of you have issues flashing. I still have it all right here in front of me if I need to make a change.
FYI: The first boot takes for ever as it registers all the APKS.
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
thorracing1 said:
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
Click to expand...
Click to collapse
So you installed both the HTC_IME.apk and the Clicker.apk? Did you do a adb push or a adb install?
Try and go into settings --> Language & Keyboard --> Touch Input --> Text Input?
I think its a force of habit with out really thinking to go there and calibrate but just going there may help.
Try that and let me know.
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
2.0t03speed said:
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
Click to expand...
Click to collapse
Awesome, keep the feed back coming as you have it!
please take note orientation doesnt work. please put in first post.
otherwise, great work!
should i do adb install or adb push?
blankd3ckskat3r said:
please take note orientation doesnt work. please put in first post.
otherwise, great work!
Click to expand...
Click to collapse
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
BTW thanks for the feed back!
thorracing1 said:
should i do adb install or adb push?
Click to expand...
Click to collapse
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
dchadwick said:
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
Click to expand...
Click to collapse
lol well its a common problem, cant wait for a fix. really like what you did with this build
dchadwick said:
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
Click to expand...
Click to collapse
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
removed SDcard.. boots now trying to push.. but where do I push the apk files to?
blankd3ckskat3r said:
lol well its a common problem, cant wait for a fix. really like what you did with this build
Click to expand...
Click to collapse
Thanks, but I really can't take to much credit. Its a "Pick and Pull" from several ROMs. This one actually came from our GSM Brothers and then I used the CDMA tricks in this form to make it work.
I keep watching and playing with the Google Nexus Dumps. I would really like to get one of them up and running.
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
VoXHTC said:
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
Click to expand...
Click to collapse
Wow thats allot in a little space.
What I gather is that it originally booted, then after trying to install via droid explorer and then astro it now just dies after the lockscreen.
I am not sure where to start. I would just say to do a full wipe, then a clean install. Then if you have the sdk try the ADB install method as Cynanogen's post talks about.
I am working on trying to get the stock Android keyboard to work. If we can figure out that then we don't have to mess with the HTC one.
ok i got it i just adb pushed them to system/app works great
obelisk79 said:
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
Click to expand...
Click to collapse
Yeah, actually some of your work if I remember correctly, thats why its got the same issues. My first goal when I built this for my self was to get past the blasted google bits sync loop. The more I worked into it the more I moved on to the 2.0.1 build with some of your stuff in it.
Your welcome to anything I have learned, its really not my work.
Hello there are rom custom for my sm-g350 pls ?
Izuna30 said:
Hello there are rom custom for my sm-g350 pls ?
Click to expand...
Click to collapse
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
ngoralph said:
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
Click to expand...
Click to collapse
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
frost245 said:
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
afaik it was moved as i have reported it
Gotta get this working!
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
AlexInHell said:
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
Click to expand...
Click to collapse
As far as I know, the lock shows, that you don't have the write permission on this file
Sent from my SM-G350 using XDA-Developers mobile app
Q&A for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Where to go from here
Not sure what happened, hope this didn't get posted twice.
Hi,
I am still happily using the Samsung Infuse 4G, and was running the stock GB 2.3.6. No real issues, and although starting to get a sense of it being dated was having no issues and in no rush to go out and upgrade. However, we recently purchased a 2015 Subaru Legacy with their Starlink multimedia system. The Infuse, as it was with the stock GB had no problems connecting via BT for phone and audio functionality. But, the car system reports that the phone is not compatible for messaging. In my endeavors to understand why, I thought, maybe incorrectly, that GB does not support the MAP profile.
So, that led me to, is it possible to add that, and how do you do it, or is it time to upgrade? Flash a new ROM? I can't seem to find much on the specific issue I am trying to resolve and if a new ROM would fix it, but since the phone is way out of warranty I decided to try rooting and flashing a ROM. I am new to this so I went with the Aeon 1.4 ROM based on GB 2.3.6 (I think), hoping that it was a bit less risky. Everything went well and seems to be working fine. But, it did not fix the messaging issue with the car. I assume because it is really still GB.
Am I going about this wrong? Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Hi there,
mainwheel said:
Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Click to expand...
Click to collapse
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
joel.maxuel said:
Hi there,
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
mainwheel said:
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
Click to expand...
Click to collapse
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
joel.maxuel said:
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
mainwheel said:
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
Click to expand...
Click to collapse
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Downloadable CM 10.1
joel.maxuel said:
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Click to expand...
Click to collapse
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
mainwheel said:
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
Click to expand...
Click to collapse
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
joel.maxuel said:
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
Click to expand...
Click to collapse
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
mainwheel said:
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
Click to expand...
Click to collapse
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
joel.maxuel said:
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
Click to expand...
Click to collapse
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
mainwheel said:
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
Click to expand...
Click to collapse
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
mainwheel said:
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
Click to expand...
Click to collapse
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Android 4.4 support for two new Bluetooth profiles to let apps support a broader range of low-power and media interactions. Bluetooth HID over GATT (HOGP) gives apps a low-latency link with low-power peripheral devices such as mice, joysticks, and keyboards. Bluetooth MAP lets your apps exchange messages with a nearby device, for example an automotive terminal for handsfree use or another mobile device. As an extension to Bluetooth AVRCP 1.3, users can now set absolute volume on the system from their Bluetooth devices.
Click to expand...
Click to collapse
Gone this far, might as well give it a shot. :fingers-crossed:
joel.maxuel said:
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Gone this far, might as well give it a shot. :fingers-crossed:
Click to expand...
Click to collapse
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
mainwheel said:
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
Click to expand...
Click to collapse
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
joel.maxuel said:
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
Click to expand...
Click to collapse
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
mainwheel said:
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
Click to expand...
Click to collapse
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I appreciate the help and will try to make some time to install these files. Will let you know. George
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Hi Joel,
Unfortunately, none of these 4.4.x versions will install, same error. And placing Voodoo/lagfix/ folder doesn't seem to work either, same error. If the problem is the jump to the next version is too great, maybe an earlier version of something, 4.2 or earlier? George
October release is available with or without root
Made a few changes as far as adding in some apk's to hopefully make it stable for everyone.
Besides that, the usual with normal default font BUT lots more choices in the font section.
Enjoy!
*if anyone has solid reasons to remove any apk files i've put back please let me know as some I should not have been removing and others... not so sure
I will no longer be able to provide new copies of this after the October security patch. I no longer own an A8 2018 and without a device to test the work, I do not feel it is appropriate to continue the project. I'd like to thank everyone that participated and I hope you enjoyed using it! If anything changes in the future that will allow me to provide the latest edited firmware, I will definitely be providing it here for you. I am using an S7 now so if you own one and like this work, there shall be downloads available there similar to this one. (Already testing).
Anyone that would like to continue on their own or have access to files used in making it I will try to include as much as possible from the link provided below by the end of October. There is currently a slightly outdated set of files and instructions (from June I believe) on how I made it already available.
Thanks Again!
Oct Security patch zip ready for download
Available with or without root AND with or without exo font - also an attempt to allow printing feature version. "Attempt" meaning I've placed a set of apk files into a separate and clearly labelled zip on the main download page that may allow proper use of the feature which has not been validated as operational by me or any other user. The "print fix" zip is rooted with exo font
This was made ONLY for the SM-A530W! Please do not use if not W (Canadian) variant. Check your phone info before attempting to flash
All ROMS/extras here:
https://drive.google.com/drive/folders/12Vwzn1CxNdT-ISsrOnSL4D353Nr14iRb?usp=sharing
The ROM will function very well and does not require any special patches, kernels, etc except obviously TWRP
Any additional issues you face with added mods most likely will need to be addressed with the creator
*Built by Superr's Kitchen*
Over 100 apps removed
***Find my mobile and pop-up asking to store lockscreen info removed- BE AWARE reduced ability to locate lost device!***
retro shutdown qmg
Overloaded notifications and ringtones
Oreo Weather (pie weather is a serious downgrade)
August Security release
FM tuner and App Lock (Next Radio may now be used starting from July 2019). Gee, THANKS SAMMY! What took you so long? Was it the polar bears?
Goofy selfie stickers that are funny... and creepy *big thanks to hadesRom genius Corsicanu for the find*
Other typical CSC changes
If your plan has wifi calling, turn it on/off once in phone settings to "break in" the qs tile
Dedicated Screen Recorder access in launcher with no shortcut style appearance (if deleted may be re-enabled with activity launcher as shortcut)
Chrome can be safely disabled at any time if desired and auto replaced with system webview
dm-verity + force encrypt already removed
Magisk rooted
Installation is easy as pie
BACK UP FIRST!
Wipe caches, data, system. Internal may be safely wiped and give the "freshest" install but is optional. Then flash away.
Once flash completes, just reboot.
-*Usage*-
You are free to use any ideas/changes included in the zip. In fact, I encourage you to do so. I've mostly pieced together work from other very difficult projects to create this. Nobody has asked me to add, remove or alter anything contained within this page or in shared downloads. Their work is everywhere and it's what made this possible.
Built with Superr's Kitchen
Some screens to sample below. yay
nobody home
empty
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Ok. I can't really suggest anything other than the obvious.
But you've let it boot once before trying, and are adding the apk as well after flashing magisk in twrp?
Hard to figure that one out. If you're using Magisk, i am assuming.
burnt_31 said:
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Click to expand...
Click to collapse
Have you tried 19.1 you may need to flash twice.
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
burnt_31 said:
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
Click to expand...
Click to collapse
I know exactly what you mean. I do it all the time.
Nice you got it going. It's pretty lame if you don't root this. I just cut it up and added a couple things and they can be taken out, except radio and the recorder.
Curious if i got it right. If you're on anything other than VMC, is call recording and other micro features working? All the cscfeature xml files are decrypted so you can see what was done.
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
burnt_31 said:
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
Click to expand...
Click to collapse
It is 168 hours no reboots and rmm did work that rmm was for Oreo.
I think his would be fine but no guarantees.
Custom kernel 2.0 flash twice.
Light rom works without issue make sure you flash magisk.
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
fabian_barrios said:
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
Click to expand...
Click to collapse
Yeah bud. If you unzip the attached file, you can place it in /system/priv-app/ and make sure the permissions are set correctly for the folder and apk. Compare with other apps in the directoty and make it the same.
Then get the activity launcher app from the play store. Use that to make a link for it.
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
boominboodhoo said:
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
Click to expand...
Click to collapse
okay thanks for that. It is probably from my csc edits. I can adjust for freedom and hope it makes a difference.
Anything else to mention about it? What you did before flashing, are you using latest twrp, root or non root.... anything at all
no-verity... favourite snack... p.i.n. number(s)... oops sorry not the last two. My mistake. TOO MUCH info. Disregard.
Do a search on xda for rooting your model for the correct version of twrp. U will need no verify no encript. I used the latest Magisk to root. Supersu did not work. I used twrp for the A8 plus and had problems. Get the right one. It's a great rom. https://www.google.com/amp/s/forum....ery-twrp-3-2-2-0-galaxy-a8-2018-t3818201/amp/
I am looking at the csc for FMC and it appears i have doubled an entry. I need to go over all of them to see if i've done it elsewhere. I will have 2 updated ones hopefully late tonight. (Takes forever to upload).
Not sure if that is the cause but i will definitely adjust it.
Quick question in regards to your Rom. I been using it for a while now. Its the best one I can find, I did post a few times at the start. By any chance, did u get adoptable storage working? I know Samsung removed it in Pie. I tried root essentials but still no luck. Thus is not my first time rooting or installing roms. I started with the HTC 1. Lol. So far, u have the best rom for the A8 2018. Its nice and clean. Almost compares with lineage in my opinion. Thanks again. And by the way, I am Canadian.
Thanks
Hey i appreciate the gesture but even though i "made" this, i did it because of other people. SuperR is an invaluable tool. Then you got magisk, the twrp recovery and heck even give ol' Sammy some credit, haha. All i did was spend time learning everything from this site. I can't stress that enough. I still have not paid for superR and i am going to see how i can right after this.
ANYWAY!
Your question. I've never attempted it but i am very certain there's a magisk module that'll do it.
It involved formatting sd to ext 4 or 3. So i will get on it. Got a few 64 gig cards to spare. If you have a computer, grab the superR linux distro. I've run it on 32 bit machines. K... pay superr... adopt a card heheh.
I will look again in the magisk module section. And I give everybody right now credit for all their hard work and sharing it amongst all of us. Thank you. Thank you. I love modding my phones and I could not do it without everybody's help. All my PC's are 64bit.
Nice. If you need any help just ask. Just bought the kitchen.
I'll have something very soon. Mexico's pie has the classic csc folder of old. I think we should unify with some fiesta pie zip ui sorta thingy... um rom.
Help please.
Noob here and I am playing with my old nexus 5 trying to get android 10 up and running on it as I drowned my daily. Currently it has TWRP v3.4.0 on it and is otherwise completely WIPED. I think I have wiped or changed the file system of the wrong partition and now I have even lost MTP access to copy new install packages across, so now I am a bit lost as to what to do next.
I got here because the nexus 5 system partition was seamingly too small for even the pico GAPPS after I installed an unofficial lineage 17.1. My intent was to make this partition large enough to try it all again.
Any direction here would be greatly appreciated.
Dan
Somehow this came good and I havent changed much that I think would effect it. At this point I think I have a dodgy usb port on the one. Its back up and running atm but my real issues are now around the n5 having too small of a system partition for lineage17.1 and gapps. Might have to try 15 or lower.