Develop Bugs

[Q] Rom Question

I'm having issues flashing multiple roms of the 4.x.x Roms. The only rom so far I have been able to install and actually run on my phone is TweakWiz V2. I have tried many other roms and they just stay in a boot loop screen. Examples are with the Avatar rom it just stays on the mask an keeps going and going. I have tried CyanogenMod/Cyan Kang an it just stays on the Circle with the bar going around on the inside.
I am running the TWRP Touch Recovery. I also have the latest Radio update and everything else is updated on my phone.
I also let the install itself run for 10+ minutes everytime. But all the roms I try they keep doing the exact same thing and staying in a boot loop.
Can anyone give me any tips or suggestions to maybe something I could do to use another rom or maybe even a suggestion to something I may have overlooked.. Any help is appreciated. Thank you.
An if you need me to give any other information let me know an I will provide.

1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash

krazierokz said:
1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash
Click to expand...
Click to collapse
1.Im using the latest TWRP.
2. Wiping System, Cache, Dvalik or whatever. I wipe everything in the usual instructions. And I make a backup of previous ROM. Flash the ROM then the G-Apps.
3. After I flash I let the ROM run its course an I wait from 15-45 mins for the ROM to load if it doesnt I switch back to TweakWiz or try another.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

try using this recovery since the recovery you are using is the latest one and technically for 4.3 ROMs, give this a shot http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.5.0.0-hercules.tar its the same recovery but lower . the steps you clarified seem very proper but your recovery may be at fault crossing fingers try flashing that recovery through odin or download the zip from the same website and report back after trying to flash again

Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.

idtheftvictim said:
Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.
Click to expand...
Click to collapse
Is there a option I'm not deleting ?
Because I've been flashing ROMS on different phones an I have never had any issues before. I was using ICS an GB etc before an just recently decided to upgrade an use the JB (I think that's the name.) on my phone.

Wifi doesn't work with any custom ROM E980

So my E980 will not turn wifi on with a custom ROM. I have tried probably 10 different roms and many different android version numbers with no change. The switch is greyed out and will not turn on at all. I have the following installed:
CM12-20150625-Snapshot-YNG4NAO09M
WildKernel
I believe Mack's modem
Gapps
Nothing will fix this. I have read where other people have installed stock Kernels to fix their issues but will doing that cause a problem because I am on android version 5.x+? Everything seems to work ok on the phone other than wifi and I really need that.

Have you tried to flash CM over full stock 4.1 without custom modem? All CM based roms recommended install is: flash stock 4.1 kdz through Lg Flash Tool 2014 cse flash, then root, then freegee + cwm, then CM. And only if something is wrong then patches.

Yeah that's how I have been doing it actually. I only started doing there kernels and stuff yesterday morning. I did find that blisspop v3.6 actually had working WiFi on my phone but it had other weird issues. It would randomly reboot and then go into reinstalling the ROM and it would also randomly shut my cellular data connection off by itself. Like I could watch it turn the switch off and on ine settings app. Those coupled with really bad battery life made me flash back to stock 4.1.2.
Then after flashing back to stock I went on and did the ota update to 4.4.2 but that caused issues with the screen not coming back on after making a phone call without doing a power cycle. I would love to run a custom ROM but none I have found are stable and only one has most all the stock features working in it.

Did you use recommended recovery version? Try upgrading from stock 4.1 directly to BlissPop using latest Philz Touch or TWRP 2.8.6.0 modified? Personally i prefer this recovery: https://www.androidfilehost.com/?fid=95916177934554356 for my E988. It can flash and backup modem and EFS.

xermit said:
Did you use recommended recovery version? Try upgrading from stock 4.1 directly to BlissPop using latest Philz Touch or TWRP 2.8.6.0 modified? Personally i prefer this recovery: https://www.androidfilehost.com/?fid=95916177934554356 for my E988. It can flash and backup modem and EFS.
Click to expand...
Click to collapse
The recovery part has always confused me. Thus far I have been downloading FreeGee Free off the playstore and using it to install CWM. I tried TWRP once but the interface wouldn't work right on my device. Some of the onscreen buttons would do different things than their label said (like Reboot would take me to a different screen, not Reboot) and the slider bar at the bottom wouldn't work.
How do you install the recovery using that Zip file? And could that be causing me problems?

Noggles10 said:
How do you install the recovery using that Zip file? And could that be causing me problems?
Click to expand...
Click to collapse
I'm installing it from recovery just like another zips (ROMs etc)
Problems? Theoretically, yes, if you flash recovery that isn't compatible with your device

Some ROMs not booting

Hey guys, I'm on vs985 and was wondering if anyone else is having the same problems I'm having. Some ROMs won't boot properly, ex. After flashing a ROM the LG logo screen appear and then goes away then the screen turns completely black. This also happens with some kernels only certain ROMs or kernel will allow my phone to boot normally. Does anyone know a solution to this? Would really like to use stock kernels on some of these ROMs. Thanks in advance

Which version of TWRP are you using, and what procedure are you using to flash ROMs and kernels? Are you flashing a different kernel immediately after flashing a ROM? Which specific ROM and kernel combinations are you flashing?

redduc900 said:
Which version of TWRP are you using, and what procedure are you using to flash ROMs and kernels? Are you flashing a different kernel immediately after flashing a ROM? Which specific ROM and kernel combinations are you flashing?
Click to expand...
Click to collapse
I'm using TWRP 2.8.3.0. And I always clean flash. Usually never dirty flash even when I'm just updating a ROM. If the stock kernel doesn't boot with the ROM I reflash the ROM along with kernel as a clean flash. The mains ones I have problems with are Exodus, BrokenOS, and XenonHD just recently. Usually the only kernel that works with any of those ROMs and allows it to boot is JediKernel 3.0. Others such as nebula, any kernel and fechda don't seem to work.

I think the first thing I would try is updating TWRP to version 2.8.7.0

redduc900 said:
I think the first thing I would try is updating TWRP to version 2.8.7.0
Click to expand...
Click to collapse
Updated to TWRP version 2.8.7.0 and still not working. Any other suggestions?
Sent from my SCH-I535 using XDA Free mobile app

Are you verifying the MD5 of the ROMs and kernels beforehand? And are you installing them from internal storage or external SD?

I don't know if this helps, but I had a lot of trouble with something that almost nobody post in ROM installation instructions: you should always format data, not just wipe it. My device is D855 International, hope it helps.

redduc900 said:
Are you verifying the MD5 of the ROMs and kernels beforehand? And are you installing them from internal storage or external SD?
Click to expand...
Click to collapse
Yeah they always match, and I install from external SD.

Try installing from internal instead.

redduc900 said:
Try installing from internal instead.
Click to expand...
Click to collapse
antony.ps said:
I don't know if this helps, but I had a lot of trouble with something that almost nobody post in ROM installation instructions: you should always format data, not just wipe it. My device is D855 International, hope it helps.
Click to expand...
Click to collapse
Tried both of these methods, still doesn't work for exodus or broken which are the only ones I really tried because I know they don't normally boot up

Trouble Flashing Custom ROM

So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.

Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later

Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)

slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew

Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.

peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew

Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew

Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!

First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs

Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]

[STOCK][7.1.1] Nextbit Robin - ether - Flashable Stock ROM [N108]

Introduction
This is a flashable zip of the latest Stock ROM for the Nextbit Robin. The boot.img is modified with removed DM-Verity and forceencryption.
It contains no recovery.img so you can continue using TWRP.
Installation
Clean flash:
- Download latest build
- Boot TWRP
- Wipe system, data, cache, and dalvik cache
- Flash ROM zip
- Flash other zips (such as root and kernels)
- Reboot
Dirty flash:
- Download latest build
- Boot TWRP
- Wipe cache and dalvik cache
- Flash ROM zip
- Flash other zips (such as root and kernels)
- Reboot
Download
ROM: https://www.androidfilehost.com/?fid=673368273298967045
XDA:DevDB Information
Nextbit Robin - ether - Flashable Stock ROM, ROM for the Nextbit Robin
Contributors
crian
Source Code: https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
ROM OS Version: 7.x Nougat
Based On: Stock
Version Information
Status: Stable
Created 2017-06-25
Last Updated 2017-06-25

Awesome thanks!

I've tried to use Substratum with this ROM but it won't work. Anyone successful?

jir591 said:
I've tried to use Substratum with this ROM but it won't work. Anyone successful?
Click to expand...
Click to collapse
It's stock and not compatible with oms.

A Mega mirror if possible? Thanks. AFH is taking too long.
I've uploaded it to MEGA
Let me know if you want me to delete the link

Hi is this stock the same and included also the 100 go memory cloud ?

Mchasard said:
Hi is this stock the same and included also the 100 go memory cloud ?
Click to expand...
Click to collapse
Yes
Sent from my Robin using Tapatalk

kwattro76 said:
Yes
Click to expand...
Click to collapse
Thanks for your answer otherwise the size of this ROM is big 1.2go oops...

Mchasard said:
Thanks for your answer otherwise the size of this ROM is big 1.2go oops...
Click to expand...
Click to collapse
That's about right. If you take a vanilla nougat rom and and then add the largest gapp package you there you have it.
Sent from my Robin using Tapatalk

kwattro76 said:
That's about right. If you take a vanilla nougat rom and and then add the largest gapp package you there you have it.
Click to expand...
Click to collapse
OK it's due to the largest gapps ... Generally I'm using pico not the largest... Thanks
Is there a way to root to delete some system apps?

Mchasard said:
OK it's due to the largest gapps ... Generally I'm using pico not the largest... Thanks
Is there a way to root to delete some system apps?
Click to expand...
Click to collapse
Just flash your favorite su app and delete some system apps.
This is just a flashable zip of the stock rom. So there are the same gapps as the factory image got.

Anyone try that unofficial xposed on this rom?
Sent from my Robin using Tapatalk

Thanks this is great. All the custom roms have too many stability bugs to be reliable enough for a daily phone. As this is stock with no recovery though, could I relock the bootloader while keeping twrp and root - therefore getting rid of the warning message on boot? Would this cause problems?

bilged said:
Thanks this is great. All the custom roms have too many stability bugs to be reliable enough for a daily phone. As this is stock with no recovery though, could I relock the bootloader while keeping twrp and root - therefore getting rid of the warning message on boot? Would this cause problems?
Click to expand...
Click to collapse
Omni and LOS works fine for me. Seems pretty table overall to me for daily use.
Anyway to answer your question, locking the bootloader will require you to flash the stock recovery which means you will lose TWRP as TWRP is the custom recovery that replaces the stock recovery.
When you root the device you are modifying the boot.img and system partitions so it won't be advisable to lock the device and try to keep root as it might not function properly and worse could brick your device. Because if anything goes wrong and your bootloader is locked there is no way to fix that issue, the point of keeping a custom recovery is so that you can fix any problem that could arise because of the modified system files.

/root said:
Omni and LOS works fine for me. Seems pretty table overall to me for daily use.
Anyway to answer your question, locking the bootloader will require you to flash the stock recovery which means you will lose TWRP as TWRP is the custom recovery that replaces the stock recovery.
When you root the device you are modifying the boot.img and system partitions so it won't be advisable to lock the device and try to keep root as it might not function properly and worse could brick your device. Because if anything goes wrong and your bootloader is locked there is no way to fix that issue, the point of keeping a custom recovery is so that you can fix any problem that could arise because of the modified system files.
Click to expand...
Click to collapse
Ok got it. Thanks for the quick answer. As for the roms, I was using Omni but I was getting crashes when using GPS (Waze) and nfc never seemed to work reliably. I switched to LOS when Omni stopped updating but I've had similar issues with it as well. Stock works well but it would be nice to have up to date security patches.

bilged said:
Ok got it. Thanks for the quick answer. As for the roms, I was using Omni but I was getting crashes when using GPS (Waze) and nfc never seemed to work reliably. I switched to LOS when Omni stopped updating but I've had similar issues with it as well. Stock works well but it would be nice to have up to date security patches.
Click to expand...
Click to collapse
I am currently using LOS but was on Omni most of the time as Omni was really stable and updated that time. But Omni started eating a lot of battery and stopped providing updates, so I switched to LOS as soon as LOS 15 was released for Robin. GPS worked fine for me on Omni too, it sometimes had problem locking the location but navigation on Google Maps worked as it should. Waze I used a few times it didn't crash that time. But not a regular Waze user.
Did your clean flash the ROM?
Can't tell you about NFC as I sadly have no reason to use it.
By the way, how is your battery? Mine is degrading bad. My SOT has gone from 3-4hrs to 2-2.5hrs. over the 2+ years of owning this device. Not only that, below 30-40% it would shut down on running any heavy app like Camera or Maps or Music Streaming. Battery is degrading badly.