Related
hi there!
i recently looked for some roms for my 9515 phone
unfourtunantly, i read here: http://forum.xda-developers.com/galaxy-s4/general/galaxy-s4-value-edition-gt-i9515-t3190176
that there are no roms for this device..
so i found another thread- http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-s4-value-edition-i9515-t3031044
which told me to download kernels, modems and other things in order 9505 roms to work.
tried it- but with no sucess.
BTW i tried to use this rom: http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
any help will be appriciated- THANX SO MUCH
ps- sorry for my english..
psII- i know that this is the forum for the 9500 and 9505 only, but i couldnt find any forum for the 9515.
psIII- i can use the phone only through PC- im using MyPhoneExplorer to mirror and control my phone.
Are you flashing a kernel right after flashing the ROM?
audit13 said:
Are you flashing a kernel right after flashing the ROM?
Click to expand...
Click to collapse
yes..
is that a prob?
edit: if i will flash stock, than kernel, and then rom- will it work?
Make sure the phone is running the latest bootloader and modem. Once that has been confirmed, perform a complete system wipe (system, cache, data) before flashing ROM, flash the ROM, and flash the kernel. Don't boot the phone out of recovery until after flashing the kernel.
audit13 said:
Make sure the phone is running the latest bootloader and modem. Once that has been confirmed, perform a complete system wipe (system, cache, data) before flashing ROM, flash the ROM, and flash the kernel. Don't boot the phone out of recovery until after flashing the kernel.
Click to expand...
Click to collapse
thanks so muchhhhh u saved my asss
how do i check my bootloader & modem version?
I suggest flashing a stock ROM from here: http://www.sammobile.com/firmwares/database/GT-I9515/
Once that is done, you can flash TWRP from here: http://forum.xda-developers.com/galaxy-s4/general/galaxy-s4-value-edition-gt-i9515-t3190176
With TWRP, you can create a nandroid backup. If you flash a ROM that doesn't work properly, boot into TWRP and restore your nandroid backup and start over.
Sometimes, you may fine a ROM that will work without further modification. If not, a custom kernel may be required.
What are you talking about? The first link you posted linked to various rom threads for the I9515.
There is unofficial CM13 for the I9515, also known as jflteve.
There also was an unofficial SlimLP..
Unofficial CM13
Unofficial CM12.1
Unofficial SlimLP
As you can see, there are some roms. No need to mess around with patchers. Unless you really want touchwhiz..
GDReaper said:
What are you talking about? The first link you posted linked to various rom threads for the I9515.
There is unofficial CM13 for the I9515, also known as jflteve.
There also was an unofficial SlimLP..
Unofficial CM13
Unofficial CM12.1
Unofficial SlimLP
As you can see, there are some roms. No need to mess around with patchers. Unless you really want touchwhiz..
Click to expand...
Click to collapse
want TW. SO BADLY
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
#Henkate said:
It's because you are flashing MM rom (except cm13) and you are on Lollipop or vice versa.
Click to expand...
Click to collapse
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
I have the same problem …
aytida4 said:
No friend actually I m using marshmallomarshmallow stock
Rom and I'm installing ressurction Rom 6.0 but still it is showing green screen. Is it the problem of BOOTLOADER?
Click to expand...
Click to collapse
SiiXFX said:
I have the same problem …
Click to expand...
Click to collapse
You must be on Lollipop to flash RR 6.0.1, just like CM13.
#Henkate said:
You must be on Lollipop to flash RR 6.0.1, just like CM13.
Click to expand...
Click to collapse
Thanks friend I will try.
Same Green Screen
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Vityy said:
I have a same problem and i try the first 5.1.1 rom and after it i install the cyanogenmod 13 which i found in the rom article anybody can help me ? skype or somthing call service ?
Click to expand...
Click to collapse
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
aytida4 said:
Friend i had that problem then i installed stock 5.1.1 rom and
Then tried this and then it is working good. U can also
Try this.
Click to expand...
Click to collapse
I flashed the 5.1.1 rom but still i get the green screen/lines at the boot. I always get bootloops when i flash any zip. Plz help
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ... ???
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
Which Custom Rom did you flash?
Keancarl said:
I have the same problem on my j500h too its turn to yellow color until the logo cant see because of that color i flashed custom kernel properly step by step 2 custom kernel i flashed they have already problem with that im running on 5.1.1 lollipop and my build number is LMY48B.J500HXXU1APA5
Click to expand...
Click to collapse
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
AndroiDTechi said:
Which Custom Rom did you flash?
Click to expand...
Click to collapse
not custom rom but kernel idk what the problem is so now i decided to have android backup in order to back again to my current system
---------- Post added at 06:46 AM ---------- Previous post was at 06:31 AM ----------
#Henkate said:
You get green screen when:
1) You flash MM ROMs (based on stock Touchwiz MM) over Lollipop and vice versa.
2) You flash MM/N ROMs (based on AOSP/CM such as LOS13, AOSIP, Mokee etc.) over Lollipop and vice versa.
3) I can't confirm this, but based on your comment, you get green screen when you flash a MM kernel over Lollipop and of course, vice versa too.
Click to expand...
Click to collapse
:good: i back to its current system now what i want is stock rom with customize and rooted system
aytida4 said:
Hey friends i am seeing green screen after flashing custom ROM and i am not able to boot into custom rom.
Phone model Samsung j500F 2015.
Click to expand...
Click to collapse
Flash 5.1.1 cynogenmod rom then install RR remix
Demicro said:
Possible problems,
- the rom is not for your device or variant
- The bootloader is for another version of Android
- Twrp was compiled with a different version of Android so are you going to get an error.
- Your bad luck exceeds an acceptable level ...
Click to expand...
Click to collapse
For those, who -as I did - don't really understand this (see the quote)...
I had the same issue when I wanted to install a custom Marshmallow ROM (6.0.1) over my stock Lollipop (5.1.1). The solution was to download and flash a new Bootloader and Modem with Odin. See tis:
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
https://forum.xda-developers.com/galaxy-j5/development/rom-resurrectionremix-v5-8-1-t3566035
iH8Ecchi said:
I just ran into this error while trying to install a custom ROM for my J500H.
My phone was running latest 6.0.1. I installed TWRP from This thread, then installed followed the instructions to install Resurrection Remix (7.1.2), but on first boot i got the green screen with the error (set warranty bit: kernel). Also tried Lineage 14.0 but doesn't work. I can still enter TWRP and download mode after getting this error.
This is my first time flashing a Samsung device. Could someone tell me what i did wrong?
Click to expand...
Click to collapse
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
wrongwriter3 said:
Sorry, first time i didn't your post till the end.
First of all.
Restore firmware with "Samsung smart switch".
You can downgrade to 5.1.1 by this instruction.
1.Flash this firmware by Odin
https://drive.google.com/file/d/0B-pt1IG7T4hmVzhuMnRyeTBjTGM/view?usp=drivesdk
(Before flashing, wipe all storages(all except internal, external in advanced wipe. If you have stock recovery, you must do both wipes)
2. After first boot flash recovery from Vince
(for both bootloaders)
3. Before flashing RR5.8.4 wipe all storages too( all, except extrnl and intrlnl)
4. Flash RR and gapps.
5. Wipe data and cache.
Click to expand...
Click to collapse
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
iH8Ecchi said:
Did you mean i have to flash RR over 5.1.1? Last time i ran into this error i was flashing it over 6.0.1, and I did full wipes within TWRP.
Click to expand...
Click to collapse
Yes.
Because it work only with 5.1.1 bootloader.
Device _a6000 1gb ram variant
By your good experience, I need suggestions for a good 32-bit ROM developed till now. Lag free running of phone, and battery backup are the main concerns.Plz suggest suitable kernel too. Replies are much appreciated. Thankyou.
Redemptioner_ said:
Device _a6000 1gb ram variant
By your good experience, I need suggestions for a good 32-bit ROM developed till now. Lag free running of phone, and battery backup are the main concerns.Plz suggest suitable kernel too. Replies are much appreciated. Thankyou.
Click to expand...
Click to collapse
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
AsCi1 said:
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
Click to expand...
Click to collapse
CyanogenMod 11 is a KitKat based ROM as far as I know and currently I am on RR 5.8.4 64-bit nougat ROM . Can you please tell does it require a specific procedure to flash from Android N to K or is it okay to flash normally like wipe > adv wipe > cache , dalvik , system / flash ROM , gapps , reboot.
Redemptioner_ said:
CyanogenMod 11 is a KitKat based ROM as far as I know and currently I am on RR 5.8.4 64-bit nougat ROM . Can you please tell does it require a specific procedure to flash from Android N to K or is it okay to flash normally like wipe > adv wipe > cache , dalvik , system / flash ROM , gapps , reboot.
Click to expand...
Click to collapse
Reverting to KitKat from Android 5.1+ (Lollipop, Marshmallow & Nougat) requires you to flash stock KitKat ROM.
Or you can try this firmware: https://forum.xda-developers.com/le...itkat-lolipop-firmware-base-switcher-t3249046
Though I haven't tested this myself, I believe it will work fine.
---------- Post added at 07:39 AM ---------- Previous post was at 07:04 AM ----------
Since you are on Nougat:
- Download KitKat firmware.
- Wipe dalvik, cache, data, system (don't wipe internal).
- Flash KitKat firmware & then flash the CM11 ROM over it.
If you choose to flash Stock KitKat ROM, do the normal flash:
- Wipe cache, data, system, dalvik & then flash Stock KitKat ROM.
Doing the latter (flashing KitKat ROM) will bring your device to the state of first, out-of-the-box, fresh boot.
What this means is that you'll have to start all over again (i.e flash recovery again).
go for official lineage by harsh
have been using it for one month or so , its flawless and works without lag
RR 7.1 May 9 build. try this. smooth for my lenovo 1gb.
Have you faced wifi problem in stock kk with mostock kernel? I can't turn on wifi , for turning on , device needs a reboot
AsCi1 said:
Stock ROM with MoStock kernel is good. Try it.
However, if you want a little lightweight ROM, you might want to try @ED300's CyanogenMod 11.
You might also like ED300's CyanogenMod 12.1 as well. However, the latest updates, I find, are a little slow on my phone.
You can also flash MoStock on said CM11, but I haven't tried it, as you have to repackage some modules for WiFi & such.
I personally am on CM11 update 11 (with no special kernel) right now.
Click to expand...
Click to collapse
Sumer_7 said:
Have you faced wifi problem in stock kk with mostock kernel? I can't turn on wifi , for turning on , device needs a reboot
Click to expand...
Click to collapse
Sorry, no such problem for me.
Try to flash ROM again.
Best of luck.
:good:
vishal_kaushal said:
go for official lineage by harsh
have been using it for one month or so , its flawless and works without lag
Click to expand...
Click to collapse
Can u plsss give the link for official lineage OS for a6000???
Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.
pissgoat said:
Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.
Click to expand...
Click to collapse
I have already replied same thing on older thread, [ https://forum.xda-developers.com/moto-g4-plus/help/quick-questions-kernel-installations-t3794980 ]
if you flash ROM, it will also install kernel which is considered stock for that installed ROM. You need to flash kernel only if you have modified it (by flashing custom kernel or SU zips).
If you want to flash different ROM, you can flash without doing anything else, just wipe and flash.
PS invictaOS is discontinued long ago, invictaOS-Nougat is stable, Oreo will be more bugfull than current available ROMs..
Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?
veikaas11880 said:
Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?
Click to expand...
Click to collapse
Though these forums are for the Moto G4 Plus, that does suggest an issue with the build of Lineage OS that you're using. Can you confirm with the developer that this build is successfully running on their device? Do you have a compatible Lineage 17 OS based kernel you could try to flash?
Was your device working with other stock or custom ROMs before flashing Lineage 17?