Database Info

[Q] Upgrading within CM

First off, like many others here, I would like to thank all the CM devs, the xda devs, and everyone else who has made it possible to run CM on the Skyrocket. I came from stock GB and the upgrade made it a new phone. You guys rock!
My question may be simple and I apologize in advance, but I am somewhat of a newb and I have made it this far without having to post a question. I have been able to search and find all my answers about installing a custom recovery, radio install, CM upgrade, and everything else associated with flashing a new ROM so I don't feel too big a newb.
Now that I have a clean install of 10.1 up and running along with the associated Gapps package, CM is telling me that 10.1.3 is available for download. My question is this...Is it safe to upgrade within CM? I am assuming it verifies the md5 hash to prevent a corrupt file from being installed? And when CM reports that 10.2 is available, how would I go about updating Gapps, since that requires a different Gapps package? Would you have to flash the new Gapps from recovery? Would it install over the older Gapps package? What about 10.2-would it have to be flashed in recovery, or would it be safe to upgrade within CM (once it becomes available)?
Thanks in advance for your replies, and thanks again to everyone who has made it possible to extend the life of the Skyrocket.

I would change CM Updater to show "Stable Only" updates for now until you become more familiar with everything. In a nutshell, yes you can use CM Updater to upgrade to CM 10.1.3.
For CM 10.2, it's currently in Nightly status and the upgrade process is more involved than just allowing CMUpdater to do the work. Go read the thread for more info. Short answer: CMupdater is perfect for nightly/stable updates of the same version (ie CM10.1.x to CM10.1.x). Don't use it for upgrading to release versions (ie CM10.1.x to CM10.2).

unfortunately, the process com.android.phone has stopped

I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick

rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Have you tried deleting the telephone system app?

rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.

rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
graphdarnell said:
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
Click to expand...
Click to collapse
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.

hardslog said:
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
Click to expand...
Click to collapse
I upgraded to the latest TWRP 2.7.0.1, deleted everything and started from scratch. Everything works great now and using new kernel that clocks to 1.8 is flying.

[Q&A] [ROM][Unofficial][CM12.1] invisiblek's CM12.1 Unofficial Nightlies [Updated 4/

[Q&A] [ROM][Unofficial][CM12.1] invisiblek's CM12.1 Unofficial Nightlies [Updated 4/
Q&A for [ROM][Unofficial][CM12.1] invisiblek's CM12.1 Unofficial Nightlies [Updated 4/9/15]
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][Unofficial][CM12.1] invisiblek's CM12.1 Unofficial Nightlies [Updated 4/9/15]. 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!

GPS?
Does the gps work on this rom?

gapps info
MC, could you provide a link to dhackers29 gapps and a little more info on deleting unwanted stuff from zip? This d2 is my DD, so I need my ducks in a row when I flash. Thanks.
Also, please reconsider this q&a bs. It's really just counter productive--that is, if you or anyone else ever even sees it.
BTW, downloaded 4/10 build with dolphin mini and it saved correctly as a zip.

darknite39 said:
Does the gps work on this rom?
Click to expand...
Click to collapse
It's working fine for me. Previously I couldn't get GPS locks on any AOSP ROM, but before switching to these builds from KitKat I flashed to Alliance ROM (stock-based TouchWiz - this is important) and got a GPS lock there. After a wipe I flashed the 4/6 build and GPS still worked.

Cool! Thank you for the tip.

Load rom from phone after wipe
Pardon my ignorance, but if i copy a rom and gapps to my phone and then do a full wipe, won't that wipe out the rom and gapps files? Is it stored in 2 different partitions, or do I put it on an external SD? I have TWRP 2.8.5, cm-12.1-20150407-UNOFFICIAL-d2vzw and gapps-L-4-15-15. Currently running cm11x.
1) Make sure you're on the latest TWRP
2) Download gapps from euroskank's site
3) Full wipe, flash ROM and gapps

Mc633 said:
Pardon my ignorance, but if i copy a rom and gapps to my phone and then do a full wipe, won't that wipe out the rom and gapps files? Is it stored in 2 different partitions, or do I put it on an external SD? I have TWRP 2.8.5, cm-12.1-20150407-UNOFFICIAL-d2vzw and gapps-L-4-15-15. Currently running cm11x.
1) Make sure you're on the latest TWRP
2) Download gapps from euroskank's site
3) Full wipe, flash ROM and gapps
Click to expand...
Click to collapse
Correct. If you put it on your internal and then wipe it the files will be gone
Sent from my Nexus 5

Advice on which version is consider to be a Stable Daily Driver
Hello everyone I'm currently using version date 4/7 however I'm having problems with Bluetooth when playing music and battery life is horrible. I'm going to try and go with 4/10 which from what I read seems to be very stable and great battery life. I simply want a good daily driver. Has anyone perform a dirty upgrade to a newer version successfully without issues. I want to perform this since it is quicker and I won't have to re-add my email exchange accounts again. How is the latest version 4/15?
Please advise,
TS

MMS and bluetooth audio (music) not working.
I'm using the lastest build 4/15 with 4/15 gapps which is running great. The only 2 problems i'm seeing is not being able to receive and send MMS and blue tooth audio isn't working properly. Are these know issues? Thank you guys for all the work that you have been doing thus far. My phone is like new again!!!
Thank you,
TS

agree textra as alternative msg app
Been using textra for about a year and like it better than stock and other apps. Would use it even if stock worked.

need to cut invisi-k a break
That's rough indeed. I for one would be fine with him doing weeklies, instead of nightlies, so dude can have time to live and work.

Latest Gaps 4/18 installation procedure.
Can I dirty install the latest gaps over our current installation or do I need to perform and clean installation of both zip files with the latest gaps? I'm currently running zips 4/15 with 4/15 gaps. Therefore can I just in recovery mode installed 4/18 gaps over the 4/15 gaps successfully without issues? Has anyone seen a big difference in the 4/18 gaps opposed to the 4/15?
Thank you,
TS

Latest Gapps 4/18 installation procedure.
Can I dirty install the latest gapps over our current installation or do I need to perform and clean installation of both zip files with the latest gapps? I'm currently running zips 4/15 with 4/15 gapps. Therefore can I just in recovery mode installed 4/18 gapps over the 4/15 gapps successfully without issues? Has anyone seen a big difference in the 4/18 gapps opposed to the 4/15?
Thank you,
TS

techysandy0504 said:
Can I dirty install the latest gaps over our current installation or do I need to perform and clean installation of both zip files with the latest gaps? I'm currently running zips 4/15 with 4/15 gaps. Therefore can I just in recovery mode installed 4/18 gaps over the 4/15 gaps successfully without issues? Has anyone seen a big difference in the 4/18 gaps opposed to the 4/15?
Thank you,
TS
Click to expand...
Click to collapse
I don't think there would be any true difference between the two gapps. I don't really see a need to update the gapps unless your updating to a newer android version. I know android 5.1.1 was released recently but I doubt the S3 could even run this version
Sent from my Nexus 5

Bluetooth (Audio) and MMS
Has anyone tested Bluetooth (Audio) and being able to send and receive MMS? Is that working successfully on the 4/19 build?
Thank you,
TS

4/22 wont boot for me!!! (Beware)
Just a heads up I just tried to install zip file 4/22 and my phone wont boot therefore I had to restore back to 4/21. I performed a full wipe before trying to install 4/22 however no luck. Yes MMS are now working on 4/21 !!!
Thanks for all the great work,
TS

I recently flashed this on my Verizon S3, however it seems that it has borked my SMS, possibly MMS (tested much less). I cannot send/receive SMS messages whatsoever. I have tried to manually set my SMSC, and have updated to the newest modem. Any ideas why this could be happening and how to fix it?

dirty flash 4/22?
anyone tried a dirty flash (I'm lazy) over 4/7? I'm stuck on "Android is starting.... starting apps". Never could get 4/15 to work. Tried dirty, clean, gapps, no gapps. Guess I'll give this an hour and then try a clean flash.

Mc633 said:
anyone tried a dirty flash (I'm lazy) over 4/7? I'm stuck on "Android is starting.... starting apps". Never could get 4/15 to work. Tried dirty, clean, gapps, no gapps. Guess I'll give this an hour and then try a clean flash.
Click to expand...
Click to collapse
I cleaned flashed 4/22 and my phone would not boot therefore I flashed 4/21 which is working well for me.
Good luck,
TS
---------- Post added at 02:18 PM ---------- Previous post was at 01:47 PM ----------
Bluetooth Audio not working using 4/21 build however I know they will get this figured out soon.
Thanks for all the great work thus far!!!
TS

Tried the 4/22 release and phone would not boot up. I got no boot animation, but eventually the Updating apps showed up. Got to the starting apps screen and after 35 minutes, nothing changed.
This was on a dirty flash. So I wiped everything and started from scratch and had the same problems. Back to 4/15 for now for me.

unfortunately process.com.google.process.gapps has stopped

hi..
i hav this problem with my tab 2 p3100..and its bit annoying me for som time nw.
i was using the cyanogenMod (CM 12.1) by @Android-Andi ..the earlest build..bt due to some soft reboot problm i changed to official cyanogenmom 11 nighties. and its respective gapps..
aftr some days its started showing "unfortunately process.com.google.process.gapps has stopped" message continuously..it was annoying ..it also shows fc messages of most of the apps installed including trebuchet app.
so i thought its a rom issue or gapps issue..so chaged by rom to stable official jellybean cyanogenmod and its gapps..but agn i encounter similr annoying problem of "unfortunately process.com.google.process.gapps has stopped" message and other apps
atlast i chage bac to Android-Andi's cyanogenMod (CM 12.1) and lollipop Base Gapps package for 5.1.1 by Deltadroid..
bt i am stll having same problem..first i thought its a sofware problm ..nw am confused whtr its a hardware problm..
please help me

I had some of this trouble once, It was fixed by installing stock rom for a few days then returning to CM11, it seems something wrong with our eMMC, may be disabling on the kernel trim caused it, on stock trim is working, Anyway on returning to CM11 it's much slower than it used to be before, So I am now with Next Rom from ketut.kumajaya, A good smooth stock based rom and could be the smoothest among stock based roms.

Hassan 4 said:
I had some of this trouble once, It was fixed by installing stock rom for a few days then returning to CM11, it seems something wrong with our eMMC, may be disabling on the kernel trim caused it, on stock trim is working, Anyway on returning to CM11 it's much slower than it used to be before, So I am now with Next Rom from ketut.kumajaya, A good smooth stock based rom and could be the smoothest among stock based roms.
Click to expand...
Click to collapse
thnks for the replay..nw am on stock rom..working fine

pauldominik said:
thnks for the replay..nw am on stock rom..working fine
Click to expand...
Click to collapse
Urw, If it doesn't get fixed for CM11, you may try Next rom, It's a non-laggy stock rom even in games it's as cm11.

Hassan 4 said:
Urw, If it doesn't get fixed for CM11, you may try Next rom, It's a non-laggy stock rom even in games it's as cm11.
Click to expand...
Click to collapse
ok...i wll try..bt crrnly i am running it on slimkat..and its wrks ok..so wll keep it runnig fr som days..

It will come back again after a few days. I haven't discovered any permanent fixes but resetting app preferences in app settings helps. If even Settings is also FCing then go to recovery do backup and restore. You don't need to have old backups, you can backup the broken ROM itself and restore it. That way you can restart and not face Settings FC. Then you can reset preferences and the problem will go away for sometime.
Issue might be lollipop or the recent stock gapps post-PA Gapps era. Stock gapps get very close to occupying system partition during installation itself. Try having a smaller Gapps and download any google app you require from playstore

[ROM][Lineage] LineageOS 7.1.2 for Samsung Galaxy SL i9003

NOTE: If you've tried to download this ROM before and Google Drive didn't let you access it, I have reuploaded the ROM directly to this post​
First, the usual disclaimer:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
About the ROM
This is a build of LineageOS 14.1 (Nougat) for the Samsung Galaxy SL (GT-I9003)
Things to take a note of
This ROM is still a Work In Progress. As such, some features do not work, as listed ahead
Make sure you keep a backup of your files. This update WILL wipe every partition (/system, /cache, /data, /sdcard).
IMPORTANT: Returning to an older ROM is non-trivial because this update applies a different partitioning scheme. To return to another version, flash the boot.img (possibly using heimdall or bml_over_mtd) of the ROM you wish to install, reboot to recovery, and flash.
ADB does not authenticate any requests. Hence, ensure you disable ADB if you're not a developer.
Steps to flash
Reboot to Recovery.
Wipe Data / Factory Reset.
Select the ROM zip from your SD Card and flash. It will reboot to TWRP.
Flash the ROM zip again. It WILL fail on this flash to let you go back to an older boot.img to stop installation if you wish to. Flash again to continue.
Flash GApps (OpenGApps pico package recommended).
Reboot. First boot can take 15mins or so.
NOTE: When upgrading from an older version of this ROM, it's recommended to wipe /system due to certain issues with the installer not updating the boot image correctly.
Downloads
ROM: lineage-14.1-20181008-UNOFFICIAL-galaxysl.zip Check the attachments on this post
Older version: lineage-14.1-20170826-UNOFFICIAL-galaxysl.zip
Things that work
WiFi
Bluetooth
Calling
SMS
Vibrator
Audio playback
LegacyCamera (no front camera)
Things that don't work
Adopted storage
Camera2
Mobile data
GPS
Video playback
Anything that is not explicitly listed as working
Tips and tricks
For forcing high end graphics (transparency in UI), add the following to build.prop
Code:
persist.sys.force_highendgfx=true
XDA:DevDB Information
LineageOS 7.1.2 for Samsung Galaxy SL i9003, ROM for the Samsung Galaxy SL i9003
Contributors
Technohacker1995, xc-racer99, Dheeraj CVR (@dhiru1602)
Source Code: https://github.com/Technohacker/android_device_samsung_galaxysl
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 14.1
Beta Release Date: 2017-08-26
Created 2017-08-26
Last Updated 2017-08-26

Known Issues:
Other than the above listed features not working, none as of now

Just curiosity- what is the sense in 7 android on so weak hardware?

dominatos1 said:
Just curiosity- what is the sense in 7 android on so weak hardware?
Click to expand...
Click to collapse
Just to show that it can be done, and a passion for reusing old hardware

Can someone pls enlighten me as soon as possible.....?? Is this ROM stable?? And it is written in the post that the status is given as Beta........ wt does that mean??.......Nd i did not understand......Why is it not possible to go back to an older ROM?? I need a detailed instructions (if pssble) how to get back to the previous ROM...... Currently iam using CM 11.......Can't I get back to my previous nandroid backup of this current ROM ?? pls answer this ASAP......Want to try how this ROM actually looks like on my GT-I9003......And i sincerely request someone to post the screens of this ROM pls..............
And would like to know wat is the difference btwn This Lineage ROM nd the Omni ROM....??

smsry said:
Can someone pls enlighten me as soon as possible.....?? Is this ROM stable?? And it is written in the post that the status is given as Beta........ wt does that mean??.......Nd i did not understand......Why is it not possible to go back to an older ROM?? I need a detailed instructions (if pssble) how to get back to the previous ROM...... Currently iam using CM 11.......Can't I get back to my previous nandroid backup of this current ROM ?? pls answer this ASAP......Want to try how this ROM actually looks like on my GT-I9003......And i sincerely request someone to post the screens of this ROM pls..............
And would like to know wat is the difference btwn This Lineage ROM nd the Omni ROM....??
Click to expand...
Click to collapse
You don't have to double post
This ROM is *somewhat* stable, however there are features missing (mobile data, GPS, video playback, etc.). Alpha and Beta are measures of how stable a version is (Alpha < Beta < Stable, in order of stability).
The reason you cannot go to a previous Android version is because I have repartitioned the phone's internal storage for a bigger /system partition and no internal /sdcard storage (it is now emulated storage). You can return to a previous ROM by flashing the stock ROM (to be more specific, the boot.img), rebooting to recovery and restoring your ROM backup.
I can post some screenshots soon, if needed
I started by porting Omni to our phone, to see if it was possible. Then I went for Lineage because it contains more features. So the Omni port is no longer active, It's recommended to use this LineageOS port.
Also, the Omni port uses the same partitioning format as older ROMs but at the disadvantage of having no system partition space for GApps and lesser fixes.
Cheers!

Thanks fr the reply!!!!
YES!!! i would love to see some screenshots.......
sorry but iam a noob at all this......I actually have another doubt too......
As u said that i should flash the stock rom..... here wt does a BOOT.IMG mean??
If u reply to this As soon as possible i would like to know wat all precautions should i take before flashing this rom.....
Bcoz this is the frst time iam seeing that u can't go back to the previous rom....
Usually i would take a nand. backup and test out a new rom nd then i wld go back to my previous backup......
Iam askin all these because the first time i flashed the Omni Rom a month before....... Nd i actually bricked my phone......
I got this "phone -exclamation-pc" icon everytime i try to get into BOOT mode or RECOVERY........
Then i recoverd safely after flashing the stock rom.......
Nd Instead of 7.1.2 for i9003 I would love to see 5.0 or 6.0 for this device......
Cant find any Lollipop or Marshmellow ROMS for the SL......
And i sincerely thank you for creating this NEW ROM for the SL.....
Have'nt seen any new ROMS lately after the CM11
(nd plssssss once think abt making a 5.0 ROM fr the SL.......What is ur opinion abt it......?? Iam sure it would look great on the SL.....)
Once again thank u for the reply.....
(ppl on xda surely are pretty friendly..... )

smsry said:
Thanks fr the reply!!!!
YES!!! i would love to see some screenshots.......
sorry but iam a noob at all this......I actually have another doubt too......
As u said that i should flash the stock rom..... here wt does a BOOT.IMG mean??
If u reply to this As soon as possible i would like to know wat all precautions should i take before flashing this rom.....
Bcoz this is the frst time iam seeing that u can't go back to the previous rom....
Usually i would take a nand. backup and test out a new rom nd then i wld go back to my previous backup......
Iam askin all these because the first time i flashed the Omni Rom a month before....... Nd i actually bricked my phone......
I got this "phone -exclamation-pc" icon everytime i try to get into BOOT mode or RECOVERY........
Then i recoverd safely after flashing the stock rom.......
Nd Instead of 7.1.2 for i9003 I would love to see 5.0 or 6.0 for this device......
Cant find any Lollipop or Marshmellow ROMS for the SL......
And i sincerely thank you for creating this NEW ROM for the SL.....
Have'nt seen any new ROMS lately after the CM11
(nd plssssss once think abt making a 5.0 ROM fr the SL.......What is ur opinion abt it......?? Iam sure it would look great on the SL.....)
Once again thank u for the reply.....
(ppl on xda surely are pretty friendly..... )
Click to expand...
Click to collapse
Will send screenshots soon
You can ignore that and just go ahead with flashing the stock ROM. The boot.img file is essentially the file that contains the boot code and recovery of the phone (in simplified terms)
The main precautions you should keep in mind are that the Internal SD card is now emulated, so wiping data will wipe any photos/music stored in internal storage. The safest place to keep your files are on an external SD card (keep your CM11 backup there, too)
The exclamation mark error is when the phone can't find the boot code, that might've been the ROM flash geting stopped partway. You can recover from that using Odin.
I actually did make a 5.0.2 NamelessROM build, but it's not very usable as such. Lollipop had an issue which used up phone RAM too much. Our phone having 512MB of RAM just made it worse. In between I was away on other tasks and so, by the time I returned, Nougat was latest. Hence, it didn't make sense (atleast to me ) to make a Marshmallow ROM when Nougat was the one in development.
You're welcome
As said above, a 5.0.2 build exists, which isn't very usable. A Marshmallow ROM doesn't exist for our phone but if one wishes to build CyanogenMod 13.0 for our device, I can give help
XDA and other internet forums are not all that friendly, just make sure you follow the rules of the forum
Cheers!

i need stable recovery for i9003

adm_83 said:
i need stable recovery for i9003
Click to expand...
Click to collapse
In the i9003 and other Samsung devices, the recovery is part of the boot partition. You can't switch recoveries independently of the current ROM (unless the main reason you want the recovery is just for the recovery or you patch the boot.img)
If you want to run a recovery, you have to get the boot.img file (taken from a ROM or otherwise) and flash it to the phone using heimdall/odin/flash_image. You'll have a recovery but it won't boot into Android.

Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1

Does it update OTA?

No news on this rom?
Inviato dal mio MI PAD 2 utilizzando Tapatalk

Yea..... what happened??
Why r there no updates??
Nd i had a question.......What do u think abt the new Android Go concept by Google for Old nd Less RAM Phones??
Do u think we'll get it for our device??

Hi,
I have the same problem. Is there a solution ?
When , i choose "Toggle script asserts" on CWM , this error disappear and the installation continue.
But at the end, the phone has a loop reboot on TWRP . No way to boot on LineageOS.
MiDi0815 said:
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Click to expand...
Click to collapse
Thank you.

LineageOS 15.1 Oreo (Go edition)
dominatos1 said:
Just curiosity- what is the sense in 7 android on so weak hardware?
Click to expand...
Click to collapse
Technohacker1995 said:
Just to show that it can be done, and a passion for reusing old hardware
Click to expand...
Click to collapse
@Technohacker1995 , do you plan to support LineageOS 15.1 Oreo (Go edition) for our devices ?
I Think it will be a great idea to get this device to work with "LineageOS 15.1 Oreo (Go edition)".
The OS is built to deal with a device with low ram and with optimized apps for better performance and lower space

Yehia2amer said:
@Technohacker1995 , do you plan to support LineageOS 15.1 Oreo (Go edition) for our devices ?
I Think it will be a great idea to get this device to work with "LineageOS 15.1 Oreo (Go edition)".
The OS is built to deal with a device with low ram and with optimized apps for better performance and lower space
Click to expand...
Click to collapse
I'm thinking of doing that, actually (more for Project Treble, rather). I can't guarantee anything though
If I get enough time, I'll try porting it over
What remains to be fixed in the 7.1 port, however, is Mobile Data, GPS, H/W Video acceleration and other features listed in the main post. The same pains would be applicable here too.
Technohacker
(P.S. MAN, what happened to XDA? It never notified me for all these posts )

MiDi0815 said:
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Click to expand...
Click to collapse
avbuuren said:
Hi,
I have the same problem. Is there a solution ?
When , i choose "Toggle script asserts" on CWM , this error disappear and the installation continue.
But at the end, the phone has a loop reboot on TWRP . No way to boot on LineageOS.
Thank you.
Click to expand...
Click to collapse
This ROM uses LVM partitions for a bigger /system partition. Hence it isn't compatible with previous partitioning schemes. I've actually added a part in the script to make sure it flashes and boots into TWRP first, because it acts as an intermediary for the actual install. You'll want to flash the ROM thrice: 1) Install LVM-partitioned TWRP (Reboots), 2) Act as a confirmation step (fails) 3) Actual install by wiping everything (should succeed) (there were supposed to be messages for each flash) .
As for a solution, if you're comfortable with Heimdall, flash the NORMALBOOT partition in download mode with the boot.img in the zip file. Then boot into recovery (TWRP) to continue for the two flashes.
Download mode is ALWAYS accessible, so don't worry, your phone isn't dead.
ryouza said:
No news on this rom?
Inviato dal mio MI PAD 2 utilizzando Tapatalk
Click to expand...
Click to collapse
I've been quite busy with other things, so I couldn't put much focus onto this.
smsry said:
Yea..... what happened??
Why r there no updates??
Nd i had a question.......What do u think abt the new Android Go concept by Google for Old nd Less RAM Phones??
Do u think we'll get it for our device??
Click to expand...
Click to collapse
It's a nice possibility, and if I'm able to get Project Trble support for the device, it'll get equal support for later releases as any other launch-Oreo device
Vershawn_Tan said:
Does it update OTA?
Click to expand...
Click to collapse
No, it doesn't, because it's an unofficial build.
Again, sorry for not responding earlier, XDA never notified me of these posts

K.....I know i may sound frustrating, but when can we expect the new update for this rom??

smsry said:
K.....I know i may sound frustrating, but when can we expect the new update for this rom??
Click to expand...
Click to collapse
I don't think it'd be any time soon, quite busy with other things, sorry :\