Develop Bugs

Stuck in boop loop after flashing stock rom with odin

I have tried flashing the stock image twice, but as it reboots it doesn't go any further than the 4g LTE screen and just loops that. Anyone have any suggestions?
I finally got it working mods feel free to delete this thread please.
Thanks

mgkaotic said:
I have tried flashing the stock image twice, but as it reboots it doesn't go any further than the 4g LTE screen and just loops that. Anyone have any suggestions?
I finally got it working mods feel free to delete this thread please.
Thanks
Click to expand...
Click to collapse
Would you mind sharing how exactly got it working?

digitalfiend said:
Would you mind sharing how exactly got it working?
Click to expand...
Click to collapse
Not at all, long story short it was an issue with my PC, I replaced some ram modules that had gone bad, and then updated my pc with windows update. I then re downloaded the image file because all the other ones were already corrupted. I re flashed and that pretty much did it.

Cannot connect to camera after root

Hey guys!
As the title says, my Camera app is no longer functioning and says "Cannot connect to camera" whenever I take a picture or switch to video mode.
Any clues?

EDIT: After a little research, the reason was as I feared: a bug in SuperSU 2.52. This forced me to go non-root for now, at least until all such major issues are fixed. We hope for the best, Chainfire!
EDIT2: I believe this is an issue with the modified boot image, as I tried everything and the camera still doesn't work.
EDIT3: I re-flashed factory everything images and when I rooted again, everything works flawlessly! Nexus 5X is a BEAST without forced encryption!

ViRb3 said:
EDIT: After a little research, the reason was as I feared: a bug in SuperSU 2.52. This forced me to go non-root for now, at least until all such major issues are fixed. We hope for the best, Chainfire!
EDIT2: I believe this is an issue with the modified boot image, as I tried everything and the camera still doesn't work.
Click to expand...
Click to collapse
I'm using SuperSU, same version, with no such issue.

Issue solved! Thank you factory images!

ROM issues

I'm pretty sure this has been asked a lot, but I'm trying to install the "TeamSPR Rom" and i'm following the steps exactly. I still get stuck on the bootscreen with the logo with the blue LED glowing. What am I doing wrong, and this happens with TeamSPR and Renegade.
Software Version: G920PVPU3CPF4
Hardware: G920P.02
Model: SM-G920P
Android: 6.0.1

Saafir said:
Wait 20 minutes.
Click to expand...
Click to collapse
My versions are correct for this right? and do I need anything else besides twrp?

steezoe said:
My versions are correct for this right? and do I need anything else besides twrp?
Click to expand...
Click to collapse
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862

Saafir said:
From the information in your post, you seem to be on the right track. That ROM has taken upwards of 25 minutes to boot for some folks. As long as the blue light is slightly pulsing, it's doing it's thing. As long as you have TWRP installed and working, you should be good to go.
Click to expand...
Click to collapse
So pulsing plus the samsung logo, is a good thing?
koop1955 said:
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
And I'm using the latest TWRP.
p.s. Thank you guys so much, I'm skepticle when it somes to asking for help on forums, cuz usually people are short tempered and or a-holes. I really appreciate it though.

1 last thing, do i install/flash the OTA part after it optimizes all the apps?

finished everything, it's booted up now, but my screen is spamming "unfortunately, "APPNAME" has stopped" is that normal?
EDIT: Can't get into my text messages either.

Saafir said:
You shouldnt receive any errors. I would reboot to TWRP, do a wipe and reinstall the ROM. Let the device boot and set it up. Once all is good with the initial install, reboot to TWRP and install the update.zip. This should ensure a nice clean start.
Click to expand...
Click to collapse
1. Flashed ROM, waited 20 is mins.
2. Phone loaded up, restarted into TWRP and Flashed the OTA zip.
3. Phone loaded up. This is when I start getting a popup saying "Unfortunately the process android.process.acore has stopped working." and my message app still won't open after i cleared cache and data.
Thanks in advance

Saafir said:
Set the device up before flashing the OTA.
Click to expand...
Click to collapse
Meaning I was supposed to wipe everything on my phone?

Saafir said:
Setup the device as go through the Setup Wizard..
Click to expand...
Click to collapse
I did exactly that. Im currently reflashing the Full ROM taking longer at the samsung screen. But I'll wait. If all else fails I'll probably go back to stock.

I'm now back to stock 6.0.1, going to give this one more go.
Would anyone mind giving me specific step-by-step directions. please?
I feel like im forgetting something crucial.

everthing finally worked out. just having an issue with xposed literally taking hours at the boot screen

Nougat 7.1.1 is rolling out!

Hey everyone, been a little while, but 7.1.1 N is rolling out to you guys.

Awesome! Is this the same 108 build that went out to beta testers?

Does it include the battery optimization that was mentioned some time ago?

***

New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?

ipowyourface said:
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
Click to expand...
Click to collapse
Is your bootloader unlocked?

Nextbit_Khang said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?

ipowyourface said:
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
Click to expand...
Click to collapse
Yeah that's kinda weird. It should work. I'll ask around.

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
Yeah, there was another person on the Razer forums who had the same problem as well.

Just got my Nextbit today updated few times before work on 7.0 present and update pending hopefully 7.1.1 , How's the update ? any issues fixed not had it long enough to find any
Sent from my Robin using Tapatalk

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.

ipowyourface said:
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
Click to expand...
Click to collapse
You had to re-lock your bootloader also, correct?

Is anybody having issues with sending text messages (your standard text message) with WiFi on? Not over WiFi, but just with WiFi on. I tried the default messaging app and the Google one. They both work the same. For me to get a text message out, I have to turn off WiFi.

I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Sent from my MotoG3 using Tapatalk

DoobyDroid said:
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Click to expand...
Click to collapse
Why don't you flash the latest factory image?
You can't flash an OTA update via custom recovery.

Loving this new update!
However, if you want to save resources and please your customers at the same time when doing the next update -
skip the nextbit bits.
Just make the next updates (if you plan on making any more of course) stock, for all intents and purposes, except perhaps for the backup/cloud feature.

revert back to 7.0 ?
since i updated to 7.1.1, my pebble 2 would constantly disconnect.
how to revert back to plan 7.0 ?
thanks!

Any word on android 8

Franzferdinan51 said:
Any word on android 8
Click to expand...
Click to collapse
Lmao very doubtful

hey there guys i'm having this weird trouble updating to 7.1.1, i'm currently on 7.0 (Robin_Nougat_88) and i have downloaded the 7.1.1 update (560 mb) and when i hit the "reboot and install" button it say restarting in 10 ... 9... 8 blah blah then rebooting now and never get to reboot... i can't install this update is there some solution? do i have to install the N108 image like new following the razer thread? thanks in advice guys have a good day!

After rooting my camera doesn't work anymore:(

hey guys
So I rooted my Exynos S20 Plus after updating it to ATE6 . Since then when I try to open camera I just get "camera error" even after restart.
I tried to use the Samsung service menu and get "unable to connect to camera service" there
Anyone else experienced this and might be able to help?
Thanks!

Did you try resetting your phone once?
If it doesn't work reflash the rom with odin

RohanKalra97 said:
Did you try resetting your phone once?
If it doesn't work reflash the rom with odin
Click to expand...
Click to collapse
Hey,
thanks for your answer.
When reflashing original firmware: Camera works.
When flashing the "vbmeta_disabled.tar" in USERDATA and the modified "KERNEL-G988BXXS2ATD5" (with Mgisk manager) as AP the camera no longer works, even after two full resets via recovery.

mautz001 said:
Hey,
thanks for your answer.
When reflashing original firmware: Camera works.
When flashing the "vbmeta_disabled.tar" in USERDATA and the modified "KERNEL-G988BXXS2ATD5" (with Mgisk manager) as AP the camera no longer works, even after two full resets via recovery.
Click to expand...
Click to collapse
"KERNEL-G988BXXS2ATD5" is for the older firmware. Please wait and it will be updated for the latest firmware.

If you follow the instructions you can make your own boot.img to suite ATE6. That will fix your camera issues
https://forum.xda-developers.com/galaxy-s20/development/howto-root-phone-s20-t4067649

RohanKalra97 said:
"KERNEL-G988BXXS2ATD5" is for the older firmware. Please wait and it will be updated for the latest firmware.
Click to expand...
Click to collapse
Wow. Sometimes I dont know if my brain is actually active and running or if its just melted or sth.
When I flashed the kernel I "checked" the number and was "ah great, the same". But well I somehow still mixed them up.
After manually packing the new boot image it worked
THANKS!!!!!!!!!

heslo.rb26 said:
If you follow the instructions you can make your own boot.img to suite ATE6. That will fix your camera issues
https://forum.xda-developers.com/galaxy-s20/development/howto-root-phone-s20-t4067649
Click to expand...
Click to collapse
Thanks, those worked like a charm!
If the image could be beneficial to someone please tlel me and will attach!