Database Info

Galaxy S4 i9500 rom written to i9505 device!!!NEED HELP.

Hi guys.I am new to forum so i didn't know where to open this thread.Also i have checked internet for a solution but never seen a dumb thing like this before in my life.So even google search engine couldn't help me about that.
One of my friend has purchased a device from dubai.it is an original device of i9505 with snapdragon 600 processor.I am personally using an i9500 octa version btw.my friend told me to check his device after he had problems with gsm service+wifi for 3g doesn't connect(or connect and drops fast) so i went to check his device.i have used some system info tools and benchmark softwares to identify the device is ok.but NO IT WAS NOT OK.all of the system info tools says that the device is i9500 but it has snapdragon processor.some idiot somehow managed to write i9500 rom to i9505 and it is working with problems.i have checked camera both ok frontal and rear.and other device properties working good as well.i should expect that it should even fail to boot but somehow working with great deal of no phone service+3g problem(phone service sometimes work i really don't know how it works or how it fails).
So i decided to make things right.Which is put the right original galaxy s4 i9505 rom to that device.i have checked sammobile and found germany version of kitkat.
general info : device is rooted.it says it has Wanamlite rom 4.2.2.
My Try list:
1)downloaded odin 3.09 and followed the instructions.(used the official rom given from sammobile.)and put the mobile to download mode(i couldn't do it with volume down+home+power button cos it is not working)but i thought i was lucky cos that custom rom had an option when i push the power button/restart/ it says there is a download menu so i choose that to put the device to download mod.after that i was hoping odin will do the job.but it FAILED DUE TO WRITE PROTECTION ENABLED on device.
2)i tried to setup cwm recovery to device(which i figured out later it was already on device but i didn't know it was there).downloaded rom manager from playstore.and i thought it would work.rom managers says i had 2 recovery programs or rom managers on the phone 1 is cwm and other is teamwin recovery.also rom manager asks me to update or upgrade cwm but it does't recognise the device cos it is i9505 with i9500 rom and rom manager couldn't identify the device as it should be.so cwm update doesn't work.also i couldn't get to the user interface of cwm which is already on the device no matter what i do.also i know old version of cwm will not make it happen for what i need to do if i was able to get in the user interface as well.i think teamwin is blocking cwm.
so on rom manager i decided to use the team win cos there is no other option for me there which puts the phone after a restart to recovery mod,the user interface works ok there but teamwin also FAILED TO WRITE THE ROM(i think it is an old version too)i couldn't say the exact version of cwm cos the device is not with me and i forget the version but team win i asked to my friend just yet and he said TWRP 2.6.00 is on it.
3)CWM i can't even get to user interface,i really don't know how to with team win there.So yeah i couldn't even give a try.
4)I am stuck.and i don't know what to do.
general user profile about me: i have a general understanding of computers,but i haven't written any rom to galaxy s4 before yet i found myself in a situation i can't handle.someone screwed up an i9505 with a i9500 rom.
ANY HELP FROM ANYONE will be very appriciated.

i have managed to upgrade tw recovery with flashify to final version but in odin still write protection is enabled in the download mod.so odin again failed.btw after upgrading tw with flashify i lost my ability to get into operating system.i just have tw recovery on the screen atm.
the rom file i tried is this one I9505XXUFNB8_I9505VFGFNB3_I9505XXUFNB8_HOME.tar.md5 which i have downloaded from sammobile.
I9505XXUFNB8_I9505VFGFNB3_VOD.zip vodafone version it says for uk.
now i have a screen of tw recovery when the device opens.strange thing is i have 2 versions of tw recovery installed at the same time.when i press volume up+home+power tw version 2.6.00 loads.
or when i open the device with only power button tw recovery 2.7 loads.no operating system yet.
i tried I9505XXUFNB8_I9505VFGFNB3_VOD.zip with tw. it gave me an error of md5 not found and failed.
what now?
anybody around there to help?
another note : i don't know if it is important or not but it says the product name is sghi337.checked google it says at-t network.is this a useful information or what to identify the problem?
all i want is any rom to make the device work again with fully functioning.

after having twrp 2.7 i tried some roms had md5 error,so after a search i wanted to try wanamlite rom wanamlite-xxufnbe-v2-4-android-kitkat-4-4-2-xposed.after installing wanamlite rom it has asked me to reboot.so i did reboot it.it had adam kernel 2.1 version.
i was expecting the device will reboot but thanks to at&t for making odin useless + making twrp useless as well.it had a message on the screen and it was written ''samsung custom'' with a locker logo open.i thought i have to wait for the first boot and be patient and after waiting about half an hour still nothing.(on the left up of the screen written red : kernel)i checked more than maybe hundreds of threads to find an answer about at&t sghi337 galaxy s4 and some ppl say i have to change the kernel.and some say i have to change it to at&t kernel i searched again for an at&t kernel i found a file name KT-SGS4-TW-JB-ATT-06-06-2013.zip.then i gave a try to that.but suddenly i realized i have lost the ability of booting to twrp 2.7.all i have left with is twrp 2.6.00 when i press volume up+home.still lucky to have it.i used that kernel reboot and got a message on the screen ''system software not authorized by at&t''.then i started searching again ppl say about loki doki.downloaded the file and flashed it on at&t kernel this time it showed samsung logo appeared and the boot sound which you know all of us familiar with and samsung led was blue.the led was like it is a pounding heart coming on and off.this should be the first load of the rom i thought again and waited and got no result.it didn't load again.failed failed and failed many times.
i also tried this file named MDOB-KERNEL2STOCK-LIB.zip.flashed it no result again.failed.this result was another strange thing.it was showing samsung custom logo boot it with sound and then turn the device off after 10 seconds.and repeats the process.reboots sounds and reboots again and again.
questions :
1) do i have a bootloader locked device?since i can't use odin to flash anything.(odin version 3.09) and if i have what can i do to fix it?
2)since i only have twrp 2.6.00 how can i upgrade it to 2.7 back with twrp.i mean twrp update using twrp.
3)with twrp 2.6.00 i used wanamlite rom kitkat version.and it says it has flashed it.but can it flash roms succesfully enough like 4.4.2?if it says it flashed everything is ok? or it misses some important features to make the rom work.what is the maximum capability of twrp 2.6.00.Do i have to try roms like 4.2.2?
4)about kernels with at&t i337 galaxy s4 what can i do?what should be the reason preventing the rom load successfully?if i have access to twrp does it mean i don't have to mess with bootloader cos i have already passed that step and got an interface for loading roms?i mean everything is ok with bootloader if i have twrp installed user interface? and after flashing a rom do i have to use the specific kernel coming with the rom or can i use any kernel for the device like stock kernels(doen't allow me to load) with loki doki or some kernels with loki doki?
i am so helpless,please enlighten me with your knowledge.any moderators or any developers can answer me?or help me?
stuck in the middle of nowhere.please help.

Getting some progress at the end!!!
Since twrp 2.6.00 is the only option i have,or i can say ''was the only option i had'' i knew i had to get an android user interface for upgrading my recovery.after a bit more search i found slimroms for android version 4.2.2 just to make the device run,and it is already loki patched.so yeah that rom flashed as lightspeed and loaded extremely fast!that worked!!! i have downloaded aptoide market since it was lacking google apps.and downloaded flashify to upgrade the version of twrp to 2.7.01.from now on i believe i can find my way to whichever kitkat rom that is loki patched would work with this recovery support.
THANKS TO SLIMROMS for making downloadable and flashable small sized roms and tnx for the guy whoever found the loki way to make it possible.Also great thanks to TWRP team!!!
PLEASE NOTE THAT : Why did i write this after no reply or no help or no messages to this thread?Because i have figured out my way reading,trying and hard pushing after failing a lot but i found my way with xda developers threads out there even no one ever replied for help.I mean thanks anyway :cyclops:

When in doubt, flash to stock ROM and proceed from there.

you mean to tell me u cant enter download mode? ask someone to press the 3 buttons together to enter it and flash the firmware specified for that S4.

[HELP] Samsung Galaxy Tab 3 SM-T111 Crashes After Rooting

Hi
After rooting my phone using Kingo Root, i installed a rom from Sammobile.com (T111XXUANH3_T111OLBANH2)
The problem is, the installation did not make my phone better. All applications started to
crash (force close) especially Facebook, Whatsapp and messaging.
The crash occured in regular basis everytime i used some functions in the apps. The warning message says: " ...... has stopped". I can not even send sms anymore since it was always crashed seconds after writing the message.
I have done all of these steps suggested in many forums but they did not work:
1. Wipe partition and cache in recovery mode
2. Delete data and cache of the apps
3. Fix permissions in apps to fix their UIDs (i used fix permission app downloaded from google play store)
My questions are:
1. What is the best installer app to install ROM from computer?
2. What is the best ROM for Samsung Galaxy Tab 3 Lite SM-T111?
3. When installing the ROM, Does it install the new kernel as well?
I'm still new in Android rooting and i don't have much knowledge about installing a new rom properly including its Kernel. Please help me to restore my phone's functions back to normal.
Thank you in advance.

robw7 said:
Hi
After rooting my phone using Kingo Root, i installed a custom rom from Sammobile.com (T111XXUANH3_T111OLBANH2)
The problem is, the installation did not make my phone better. All applications started to
crash (force close) especially Facebook, Whatsapp and messaging.
The crash occured in regular basis everytime i used some functions in the apps. The warning message says: " ...... has stopped". I can not even send sms anymore since it was always crashed seconds after writing the message.
I have done all of these steps suggested in many forums but they did not work:
1. Wipe partition and cache in recovery mode
2. Delete data and cache of the apps
3. Fix permissions in apps to fix their UIDs (i used fix permission app downloaded from google play store)
My questions are:
1. What is the best installer app to install ROM from computer?
2. What is the best ROM for Samsung Galaxy Tab 3 Lite SM-T111?
3. When installing the ROM, Does it install the new kernel as well?
I'm still new in Android rooting and i don't have much knowledge about installing a new rom properly including its Kernel. Please help me to restore my phone's functions back to normal.
Thank you in advance.
Click to expand...
Click to collapse
If you're installing a stock ROM use ODIN always if its a Samsung device, if it's a custom ROM use a custom recovery like CWM or TWRP.
When installing a custom ROM it will install a new kernel most of the time (Very rare when a ROM doesn't contain a kernel and it's always custom ROMS). A stock ROM will always contain a new kernel.
Finally there is no such thing as a "best" ROM, everyone has a personal preference but to get you started I would recommend trying out CM11, Paranoid Android or PAC-ROM as these have a nice stock feel whilst containing useful tweaks.
To restore your phone to stock just download the stock firmware from SAM Mobile and flash using ODIN and select the PDA file in the PDA button area and then flash

TechMinerUK said:
If you're installing a stock ROM use ODIN always if its a Samsung device, if it's a custom ROM use a custom recovery like CWM or TWRP.
When installing a custom ROM it will install a new kernel most of the time (Very rare when a ROM doesn't contain a kernel and it's always custom ROMS). A stock ROM will always contain a new kernel.
Finally there is no such thing as a "best" ROM, everyone has a personal preference but to get you started I would recommend trying out CM11, Paranoid Android or PAC-ROM as these have a nice stock feel whilst containing useful tweaks.
To restore your phone to stock just download the stock firmware from SAM Mobile and flash using ODIN and select the PDA file in the PDA button area and then flash
Click to expand...
Click to collapse
Thank you for your reply but can i just replace my current ROM with correct custom ROM that will not make my phone crashed? I have installed the stock firmware but it did not make my phone any better.
I have also installed dr ketan custom ROM but still the phone functions not working properly. All apps crashed after only a few seconds opened and sub menu can not be accessed.
I wish someone can help me fix this because i have only one phone i use for work.
Sorry about my English and wrong term i use.

robw7 said:
Thank you for your reply but can i just replace my current ROM with correct custom ROM that will not make my phone crashed? I have installed the stock firmware but it did not make my phone any better.
I have also installed dr ketan custom ROM but still the phone functions not working properly. All apps crashed after only a few seconds opened and sub menu can not be accessed.
I wish someone can help me fix this because i have only one phone i use for work.
Sorry about my English and wrong term i use.
Click to expand...
Click to collapse
If you have the correct custom recovery installed and the correct custom ROM on an SD card sure you can replace the current one

using kingo withot issues
no offence but using kingo from last 20 days, typing fm same 111 tab, but no isssues, not installed cwm,twrp(actally thry r giving only bootloops) hense stock recovrry 4 now, so apps who depends upon cwm.... cant run
major problem cant write SYSTEM PARTITION.

AOSP 4.4.4 D2303 Work In Progress

Hi again all.
Another barebones AOSP for our D2303's. This time it's Kitkat (4.4.4). Again it's using Stock kernel and totally unadulterated code (as-is off the repo). This ROM was built using the Sony guides & is a demonstration that it is doable.
I have not tested this ROM yet, I will be later on tonight when I get time to TWRP backup my LP.
This ROM sort of works!
* Wifi, BT, Data, Calls, SMS work
* NFC does not for me (does on 5.0.2 though)
* Sensors do not appear to be working
* Still no camera or loudspeaker on call for me
* Few UI glitches (menus jumping left and right)
5.0.2 is more stable, however this is more responsive in general.
Flash this the same way as 5.0.2 in my other post. If you want to take a backup first, using the boot.img from OmniROM 4.4.4 for the D2303 and use "fastboot boot boot.img" - Remember not to flash (we dont need to keep this kernel, although it //may// work with this ROM, no idea) - We just boot and hit volume down repeatedly during Sony logo and get into recovery.
Root by flashing SuperSU.zip using TWRP boot method. xPosed by normal means after rooting.
Magnet Link - Please be patient - May be slow to start until more people seed
Links temporarily removed. Please read comments. Back soon
Extract the .TGZ
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
MD5's
cf5c641c4b3a8d179a6ef39d856852b7 boot.img
5a27597159c5c65d82f3fd18a0dcaca6 system.img
336148800f5c010a1654e55087cc01ae userdata.img
I am not sure of the modem requirements of this ROM. It may work on a 4.4.4 modem, but to be safe and cautious, using a 4.4.2 should be safe (as a 4.3 should hopefully be). However, I have so far found the 4.4.4 modem just does not get on with LP. You may have diffent mileage with different modems (4.4.4 for example). I am still using a 4.4.2 modem and don't really want to go flashing a modem again to only flash back. I will be going back to the LP
Again no idea if this ROM works yet
I will test later on tonight, but I put the link up for others to try. I will give this a shot later & give it a good bashing.
Use this ROM purely at your own risk
Please feedback any success or failures.

Can you upload on MEGA? :'(

Mega link added
This time the boot.img is the proper one
I still havent tested this ROM yet, the missus and I were Ingressing all night. If anyone has tested, can they give a little info of their experiences please?
Tested it, and it's got a few shortfalls for me.. I've updated the OP to show.
Am now going to build 5.1.0 - why not eh?

Can you develope the CM11?
Sent from my Xperia M2 using XDA Free mobile app

So its ONLY for d2303?

I have to say yes for it being only for the d2303. Without another variant of the handset or anyone to test, nobody can say for sure. Sorry about this, blame Sony.
I only tinker, Galaxyfreak is the best guy for CM work
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

I can be there for testing part for d2302 model if you try to port it to d2302.. @Dutch Burdock

Ive removed the download links as I noticed why this ROM is buggy. I did not clean out the old build and the kitkat is using binaries for LP. I will rebuild again soon and repost. Sorry for this.
As for the testing on other devices, since I am not a developer, the only thing I can suggest is you take a good backup and try flashing one of these ROMs (my 5.0.1 build is the most stable minus camera.) I would like to think itd work, minus second sim function, but i have no way of knowing unless someone braves this attempt. BACKUP IS IMPORTANT. Flashtool is your friend.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app

Don't think it would work otherwise it would be in the device tree. It's not a lte model so would not boot up dual is only 3g and 2g
D2303 stock 4.4.4 KK rooted philz touch recovery xposed Bravia engine 2 x-reality

Sony sucks..!!

Mobile network not working after flashing Gionee ROM - BLU Pure XL

I was trying to update my BLU Pure XL via OTA. I had TWRP and my phone was rooted, so I had to flash a ROM so I could be able to do an OTA update. I was dumb enough to not make a back up before flashing the the Gionee ROM using SPTool. Even worse, I formated the whole phone. The flashing went OK, and I was able to use my Phone with this ROM installed. Then I saw I wasn't getting reception. So I checked the APN and it recognized my sim card but still I was not able to use LTE, make calls or receiving and sending messages. I live in Mexico but I didn't had any problems at all when using the ROM that came with my device. I have also tried flashing the Allure ROM but it didn't fixed my problem either.
What can I do to fix this problem?

PSD6511 said:
I was trying to update my BLU Pure XL via OTA. I had TWRP and my phone was rooted, so I had to flash a ROM so I could be able to do an OTA update. I was dumb enough to not make a back up before flashing the the Gionee ROM using SPTool. Even worse, I formated the whole phone. The flashing went OK, and I was able to use my Phone with this ROM installed. Then I saw I wasn't getting reception. So I checked the APN and it recognized my sim card but still I was not able to use LTE, make calls or receiving and sending messages. I live in Mexico but I didn't had any problems at all when using the ROM that came with my device. I have also tried flashing the Allure ROM but it didn't fixed my problem either.
What can I do to fix this problem?
Click to expand...
Click to collapse
Check page 31 of the BLU Development thread in this forum towards the bottom of the page @thebirdguy has posted a TWRP backup of the BLU pure xl ROM. Just download that, flash TWRP to whatever ROM your on now and restore using the backup you just downloaded.

droidboy29 said:
Check page 31 of the BLU Development thread in this forum towards the bottom of the page @thebirdguy has posted a TWRP backup of the BLU pure xl ROM. Just download that, flash TWRP to whatever ROM your on now and restore using the backup you just downloaded.
Click to expand...
Click to collapse
Thank you for your quick reply. I have already restored the backup he uploaded but still no luck, perhaps it has something to do with another partition other than system and boot.

PSD6511 said:
Thank you for your quick reply. I have already restored the backup he uploaded but still no luck, perhaps it has something to do with another partition other than system and boot.
Click to expand...
Click to collapse
No luck as in you still have no mobile data or can't make calls or texts? Do your IMEI's say invalid?

Were you able to get it working?

[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 :\