So I follow the instruction, flashed the bumped bootstack, the resurrection remix rom and recommended gapps, but no matter how many times I tried, the phone simply hangs at LG logo. Does anyone knows what the issue might be? Oh, my model is d800.
On d800 you need the loki LP bootstack, but be sure to flash back to bumped before you flash a stock based rom like cloudy
kansasboy001 said:
On d800 you need the loki LP bootstack, but be sure to flash back to bumped before you flash a stock based rom like cloudy
Click to expand...
Click to collapse
I have tried using loki lp bootstack but when I do I just get an error message when flashing the rr rom zip.
Make sure you have the 5.5.5 version. It is NOT at the bottom of the list on afh. 5.5.5 will not error
Related
So, I've been reading a whole load about the G2 D801. I have stock rooted with TWRP Lollipop D80130B. What do I have to do in order to flash CM12.1 or any AOSP ROM if coming from Lollipop. I was reading something about flashing a Lollipop bootstack and any ROM, but I need a more thorough explanation. Just got this phone and I'm not trying to brick it lol. Anyone explain to me, please?
Ok for some reason canada always gets the shaft for custom roms.well i have been flashing d855 roms on my d852 since the lg g3 came out.well i notice all the custom roms on marshmallow so i decided to experiment. So there are custom mm kernels for our d852 but no roms.now this sounds crazy but all the stock kernel would not boot my phone.only fastboot mode.I decided to flash aosp nebula kernel Rev 12.3 on Fulmics 3.5 stock marshmallow rom and it booted.I chose d855 in aroma and flashed flashed the nebula kernel.I flashed multiple d855 mm roms withe d852 nebula kernel and all booted with no issues.Enjoy
jamesrfraser said:
Ok for some reason canada always gets the shaft for custom roms.well i have been flashing d855 roms on my d852 since the lg g3 came out.well i notice all the custom roms on marshmallow so i decided to experiment. So there are custom mm kernels for our d852 but no roms.now this sounds crazy but all the stock kernel would not boot my phone.only fastboot mode.I decided to flash aosp nebula kernel Rev 12.3 on Fulmics 3.5 stock marshmallow rom and it booted.I chose d855 in aroma and flashed flashed the nebula kernel.I flashed multiple d855 mm roms withe d852 nebula kernel and all booted with no issues.Enjoy
Click to expand...
Click to collapse
Sorry guys.on a couple roms you loose baseband so you need to flash the rogers lp modem.Yes it actually works.full lte with data working
Just curious if anyone eslse has tried my methods?Works well with Tizen rom V5 marshmallow.choose d855 in aroma.flash.then untick reboot device enorder to go back to twrp(2.8.7 by the way)wipe all catches then flash the nebula kernel then your baseband or modem then reboot.All works with no issues yet.nothing broken.Only sharing my own experience and experimenting.Flash at own risk
You are courageous and bold. I am going to wait for the official version before I try. I did have CM13 for a while but wanted the stock experience to test out the banking touch and pay thingy. I have heard and seen too much trouble with reckless experimentation. kudos to you for taking the chances and finding a solution.
I've tried this method and it works fine. I usually do it with the d851.
However, BlackSoulsxxx just put out his d852 port recently. I've been using it for 2 days now, no problems. Smoother than ever.
jamesrfraser said:
Ok for some reason canada always gets the shaft for custom roms.well i have been flashing d855 roms on my d852 since the lg g3 came out.well i notice all the custom roms on marshmallow so i decided to experiment. So there are custom mm kernels for our d852 but no roms.now this sounds crazy but all the stock kernel would not boot my phone.only fastboot mode.I decided to flash aosp nebula kernel Rev 12.3 on Fulmics 3.5 stock marshmallow rom and it booted.I chose d855 in aroma and flashed flashed the nebula kernel.I flashed multiple d855 mm roms withe d852 nebula kernel and all booted with no issues.Enjoy
Click to expand...
Click to collapse
That's strange that you would encounter these problems. I have the same model (the D852) and I flashed a nightly of CM 13 on my phone and so far, everything is working. The only issue I've experienced is that sometimes, when a call is coming in, I don't notice it happening at all. After the call goes to voicemail, I got notified about a new voicemail message, but in my call history, I don't see the missed call. Aside from that, data, calling and all the other usual stuff seems to work fine.
TemporalArc said:
I've tried this method and it works fine. I usually do it with the d851.
However, BlackSoulsxxx just put out his d852 port recently. I've been using it for 2 days now, no problems. Smoother than ever.
Click to expand...
Click to collapse
Do you have any link for the port?
RapHaeL_4_4_4_ said:
Do you have any link for the port?
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/rom-lge-d855-android-marshmallow-ported-t3285025
First post, under the downloads section. It's hidden under the changelog. Took me a moment to find it as well.
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.
Hi guys I have rooted my YU yureka cm 11. Its been 2 days I am trying to flash twrp on my device using both twrp official app and twrp manager. I have tried 3.1,3.0,3.02 versions while flashing. After flashing it says successfull but when I tried to reboot into recovery the mobile stucks on YU logo I think gets bricked this is what happening every time
CM11?
Any reason to sticking with CM11?
It is a 32 bit ROM and TWRP you're trying to flash is 64 bit. It won't get flashed ever.
Better install COS12.1 or any other custom ROMs.
There is no any specific reason for sticking with cm11 I thought it is most stable.
So is there any way I can flash twrp?
Or do I have to upgrade to cm 12.1 and then try to flash?
Can you recommend me any rom with better stability for yureka?
First try to upgrade to COS12.1 and than flash TWRP.
There are lots of N custom ROMs available and is stable. You can find more about them here or at YU Forum.
minestrome said:
There is no any specific reason for sticking with cm11 I thought it is most stable.
So is there any way I can flash twrp?
Or do I have to upgrade to cm 12.1 and then try to flash?
Can you recommend me any rom with better stability for yureka?
Click to expand...
Click to collapse
Flash Cos12.1 via fastboot, as it will change ur architecture from 32bit to 64bit...
Then check bootloader status, and if locked, unlock it as well, flash TWRP and enjoy custom ROMs,
Nougat ROMs are much stable now
For any problem, feel free to ask,
Thank YOU
thanks
Thank you very much guys , your help is very very appreciated.