Boot crash omni-7.1.2-20171018-ether-WEEKLY - NEXTBIT - Omni Q&A

Boot crash omni-7.1.2-20171018-ether-WEEKLY - NEXTBIT
Using the omni-7.1.2-20171018-ether-WEEKLY on a brand new, out of the box Nextbit Robin. I followed the install process posted at https://forum.xda-developers.com/nextbit-robin/orig-development/rom-omni-20160721-t3423514 to the letter, the device boots to the OMNI animation, then a series of error screens pop up. Clicking through the successive screens, it is evident that there are 3 errors are looping. One is GUI, and I did not note the others.
I suspect my error might have been installing magisk before installing the rom.
Had I done something wrong? or does this ROM have issues with the Robin?
Originally posted to the Nextbit Robin forum.

Related

GApps not working

First of all, hello all!
I'm a new member here.
So, what's the problem? Well, I recently rooted my Galaxy Tab 4 SM-T530 (WiFi only version) with Kingroot. Then I installed Cyanogenmod from the thread listed at the ROM section. All was working fine up until I decided to flash the GApps.
I chose the newest versions (both Zero and Mini for 6.0) but none of them worked.
Flashing went well. The problem was after booting.
After the first boot, I'd get caught in an endless loop of errors stating that "Unfortunately, Setup Wizard has stopped working". I couldn't do much other than rebooting. But then, I was greeted with yet another problem: it was stuck in a boot loop. Basically, after saying that it "Prepared Google App" and some others, the tab would repeat the process in an infinite loop. I left it for half an hour to do so, but the problem persisted.
Keep in mind the fact that I installed the newest version of Mini GApps package provided from that thread.
If any of you can help me out with this, I'd be very thankful, since this is the same time I install a custom ROM, and I really don't want to come back to the old Samsung ROM
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
This is from where I installed all things needed.
Try again, this time flash both zips at the same time and not doing anything in the middle of both flashes. The usual cause of the same error in my other s3 is booting the ROM up, going back to recovery, then flashing GApps.
I never did anything else. Now I wiped data/dalvik/system/cache, reflashed the ROM and now just finished reflashing both zips in TWRP (first Mini then Zero, can't do them at the same time).
Now, I'm pretty much 'fingers crossed', as this is what an error told me. Pretty much tried to flash the zips without wiping anything/reflashing the ROM. That's why I went for a clean install.
EDIT: it didn't work at all. Still caught in the same "Preparing app x" boot loop. Now I'll let it run for 6 hours and see if not my own impatience is the problem.
EDIT 2: For some reason it took ages to boot up. Now, when I finished booting, I saw that the Play Store, Quick Search Bar and the Google Services weren't working at all. I tried to manually update them, but ended up in an agonizing loop of "Unfortunately, Google Services Framework has stopped" errors. Again, this leads me into thinking that the GApps from that thread aren't working.

Samsung Galaxy Tab 4 10.1 (SM-T530NN) experiencing SEANDROID NOT ENFORCING message

Hello XDA! I recently came into ownership of two Galaxy Tab 4 10.1 WiFi tablets that came factory reset with Android 5.0.2, they are the SM-T530NN variant for education as these came from a school - and I wanted to flash them with LineageOS. I had already rooted and flashed my Nexus 7 with LOS with no issues and really like it, so I figured I would do that too on these Tab 4's.
The problem I am running into is once I install LineageOS and Supersu from TWRP, the tablet reboots and can't get passed the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
I've read that this is not an error, and has something to do with the rooting process or possibly the ROM that I used itself, but nonetheless, it just sits at that error and never fully boots, hence why I can't just ignore it. My OS appeared to install with no errors. Other posts that I have researched on this forum concerning that message don't fully provide me with a solution I can replicate. However, I still have access to download mode and TWRP recovery upon boot so all does not appear to be lost.
I started with thisisapoorusernamechoice's guide (which was awesome by the way) for rooting and have kinda gone from there, trying newer version's of TWRP but am still stuck at boot.
Here are the files/versions I have used:
Odin 3.11.1
twrp-3.0.0.9_matisse_20160314-0843.tar (and 3.0.3.0)
lineage-14.1-20170319-UNOFFICIAL-matissewifi
supersu 2.79
Any help would be greatly appreciated.
***UPDATE***
Never saw any replies to this post so I decided to just try a different ROM, went for Bliss 6 to see if it would boot. Sure enough I still get the same message as before but it does boot up and is usable! Some minor things are not working like the camera app crashes upon opening, and the lock screen date and time are all smashed together - but these are minor inconveniences as these tablets will only be used for Plex, not taking pictures. Plus I still have a TWRP backup of the stock ROM should I choose to go back to that.

[H990N][HK] Massive crash applications on startup

Hello everybody,
To introduce my problem, I explain the situation. I buy a V20 H990DS that I tried to root but with no succes. In my trial, I do some many fatal error like erase boot and aboot partitions.
I send my phone to after sales services and they repair my phone. They changed the motherboard and now, I'm with a v20 H990N.
The first startup, i get some many application don't work and literrally crash like gallery, camera etc... I do a factory reset and upgrade the firmware with LG BRIGDE to Oreo. Everything passed good and I start use the phone (no apps installed, just testing). But, some app start crashed but less frequently.
So, I decided to root and tried another stock firmwares. But each times, I have some app crashed. My last crash, in the configuration start step, is about the EULA app and crash at the end of configuration which has the effect to restart the start configuration and you can never finish the configuration.
I tried different kernel, too, like mk2000 or DOTS but same thing.
I tried different custom rom, too, like resurrection or lineage (for h990ds) but each time, I have errors during installing zip in TWRP.
Actually, I'm in TWRP 3.2.3 like recovery, DOTS like kernel and I will try the latest Oreo zip root flash.
Have you encountered this kind of problem too ?
Thanks for help !

i9506 crashes with blue screen

Hi, I've had a S4 LTE for over a year, tried quite a few different roms on it and eventually settled for Diamond John's RR 5.8.5 version. This was working more or less okay until a few weeks ago when the phone crashed during some activity with that blue screen thing.
After that I could not start the rom properly again, it always either boot loops or displays the blue screen. I then tried reinstalling the rom, other roms, bootloader and eventually the stock rom but it still behaves the same - crashes, bootlops and/or blue screen.
I think I did follow the recommended procedures, ie wiping everything, starting from scratch and using appropriate files but can't be 100% sure since I'm not an Android wiz. Hence my question: do you think there is something else I can try to recover this phone or does this look like hardware failure?
Thanks in advance

Missing a step..

Could use some pointers, as it's been a while since I have ever tried to root/flash a GSI image (last time was my old phone running Oreo), and this is my first Pixel.
Did searching, and tried a few things, but am running into a hiccup -
Following this message here:
Using the vbmeta.img from this post, and downloading an AB GSI image, following those steps will cause my phone to boot up, play the initial Google logo, and then get locked on the "G" logo on white screen, never getting into the ROM.
For some reason my memory is failing me, and I feel like I'm forgetting something - or am I using (a) wrong method somewhere?
Thanks all-
Mike

Categories

Resources