Database Info

So what did I screw up ?

After a run in with a couple of apps' who's developement ran out with ICS 4.03 (VLC Media player and Tesla paid flashlight),I managed to recover once (VLC),but after Tesla I couldn't.
Along with usual house cleaning after root,I did Uninstall KNOX and it's buddies ... 4 in all,IIRC.
Chrome Cast is also gone.
Here's where it seems to have gotten weird: when I put in Tesla the instability got so bad that I was forced into a factory reset.
There went my root.
Upon trying to redo it,I can finish the first step of rooting,but the second step fails.
I'm guessing because of KNOX?
I have older backups,but I can't boot into recovery to access them ... no TWRP.
Any ideas on this one,or am I looking at sending it in for a reload?
Any help would be appreciated.

No ideas?

No idea
---------- Post added at 03:32 AM ---------- Previous post was at 03:00 AM ----------
I wish I could help

No problem ..... I'm running 5.1.1 now.
MUCH better than 4.4.4 and just as easy on the battery..... snappier too!
I think it's the T Mobile ROM.
I had it installed at CPR in Novi,Michigan when I was down for the Woodward Dream Cruise.
Now to root!
Not sure if they're up to that point yet?
I've even turned off KNOX active protection .... it's in the settings.:highfive:

No TWRP and no back up accessable
You can download the stock Firmware from [www dot sammobile dot com/firmwares. You will be able to flash this using Odin and will #1. Restore you boot loader to factory. And #2. Will restore you KNOX, which will show un-altered. From here of course install your TWRP and should be able to proceed as normal.

I looked and it seems they're only offering 5.1.1.
My question would be:can you go back to KitKat after upgrading to 5.1.1?
If I could,where would I find the ROM?
Lastly: I like this system much better than the stocker.
The downside is the O/S uses around 1 gig of memory.
THAT'S BLOATWARE!
I've got 34 app's disabled right now.
I'm thinking it'll easily be under 430 megs once I get rid of the garbage.

[FIX] No signal after update/flash to 6.0 (MM)

Hello, everyone. It's been a long time since I posted, maybe since my S4.
There may be some of you who are not getting signal or just "Emergency Calls Only" after update/upgrade/flash to 6.0 (MM).
There's a simple solution which I found after many and many tries.
Modem: https://www.mediafire.com/?14az40tk2dkd3gw
Step 1. Download the Modem attached.
Step 2. Open Odin, look for the file and put it in CP.
Step 3. Flash it.
Step 4. There's not step 4.
Enjoy your signal.
Edit:
If any of above does not work you can use this method by dhiru1602
Happened to me. I had no signal after flashing Marshmallow. Reverting back to any lollipop baseband fixed the issue. I did some digging and it turns out there was some provisioning parameters changes done from Lollipop to Marshmallow which was preventing network to work after flashing Marshmallow baseband. The RIL was using the wrong radio technology setting.
I did the following to fix the issue.
1. Dial ##72786#
2. Press Yes to reset the Provisioning Settings to default.
3. Reboot the Phone.
CAUTION: I am not responsible for broken unlocks. I tried this method and my phone was still unlocked. I don't know if it works for everyone without breaking unlock..
Click to expand...
Click to collapse
If you have any questions don't be afraid to ask, we are here to help and since Nougat is out there may be many bugs like Uber eating the battery away.

About to try this, havent had signal for 2 days now and it would only reboot after about 2 minutes even with airplane mode on. Weird thing is one time itd boot with a signal bar icon area and the next time it would be gone completeley and so on back and forth. If this works you are my hero.
---------- Post added at 04:55 PM ---------- Previous post was at 04:47 PM ----------
Will this work for lollipop and Marshmallow?

droseofc said:
About to try this, havent had signal for 2 days now and it would only reboot after about 2 minutes even with airplane mode on. Weird thing is one time itd boot with a signal bar icon area and the next time it would be gone completeley and so on back and forth. If this works you are my hero.
---------- Post added at 04:55 PM ---------- Previous post was at 04:47 PM ----------
Will this work for lollipop and Marshmallow?
Click to expand...
Click to collapse
It's the lollipop radio, so it will work fine, and yes, it will work in Marshmallow, tested by myself.

Is there anything i need to do first? After flashing lollipop or marshmallow my phone will start and stay on for about a minute with no signal and then reboot and do it all over... ive done factory reset. Turning airplane mode on delays the reboot but will end up rebooting. The area for signal bars is there just no bars
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
Should i do rtn for sprint clear efs and have modem in cp slot with the lollipop or marshmallow in ap slot or do separately? Sorry for blowing up thread i just dont want to resort to calling sprint with no resolution from them.

To check if it's a situation about CPU reboots install TWRP and put the phone to do some random operation that TWRP has, if it does reboot even in Recovery then your phone is faulty, if not then let's do something about it, I wil guide you.

Sweet i appreciate it, im flashing marshmallow back on then i will flash twrp, the sim card wont react when putting one in or out such as requiring a reboot. I just called sprint and they set an appt but id rather not. I will post as soon as twrp mode and let u know if its rebooting there.
---------- Post added at 06:49 PM ---------- Previous post was at 06:41 PM ----------
Im in twrp mode now, no reboot so far
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Basically in a nutshell how it happened is I upgraded to marshmallow via oden and everything was good, signal everything. So then i installed twrp 3.0.0.0-3 or what ever and through twrp installed supersu 2.68 and rebooted and thats when signal was gone. Reflashed marshmallow via oden and same issue up til now. Have flashed ok3 and marshmallow with no fix.
---------- Post added at 08:06 PM ---------- Previous post was at 07:20 PM ----------
I now have tried installing moar rom through twrp and it bootloops about the same timeframe it would reboot in stock only not getting fully booted but rebooting while the boot animation is going where the stock would fully boot and then about 30 seconds it would reboot. Flashing stock would successfully boot the first time and then the 30 second reboot, flashing custom reboots 30 seconds still only not fully booting the first time. Sim status and imei status have no information on stock and software version shows unavailable on stock with both lollipop and marshmallow. The only place it doesnt reboot is twrp or philz touch or stock recovery

droseofc said:
Sweet i appreciate it, im flashing marshmallow back on then i will flash twrp, the sim card wont react when putting one in or out such as requiring a reboot. I just called sprint and they set an appt but id rather not. I will post as soon as twrp mode and let u know if its rebooting there.
---------- Post added at 06:49 PM ---------- Previous post was at 06:41 PM ----------
Im in twrp mode now, no reboot so far
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Basically in a nutshell how it happened is I upgraded to marshmallow via oden and everything was good, signal everything. So then i installed twrp 3.0.0.0-3 or what ever and through twrp installed supersu 2.68 and rebooted and thats when signal was gone. Reflashed marshmallow via oden and same issue up til now. Have flashed ok3 and marshmallow with no fix.
---------- Post added at 08:06 PM ---------- Previous post was at 07:20 PM ----------
I now have tried installing moar rom through twrp and it bootloops about the same timeframe it would reboot in stock only not getting fully booted but rebooting while the boot animation is going where the stock would fully boot and then about 30 seconds it would reboot. Flashing stock would successfully boot the first time and then the 30 second reboot, flashing custom reboots 30 seconds still only not fully booting the first time. Sim status and imei status have no information on stock and software version shows unavailable on stock with both lollipop and marshmallow. The only place it doesnt reboot is twrp or philz touch or stock recovery
Click to expand...
Click to collapse
Try the directions in this post http://forum.xda-developers.com/showthread.php?p=66040143

954wrecker said:
Try the directions in this post http://forum.xda-developers.com/showthread.php?p=66040143
Click to expand...
Click to collapse
Try the general steps but flashing the official firmware or using the one from that thread? The biggest issue currently besides no signal is the rebooting every 30 seconds unless im in download mode or recovery be it twrp or stock. The software version under settings and status shows as unknown as well as sim status and imei status on both lollipop and marshmallow. If i could get it to stop rebooting i could play around in hidden menu or build prop or csc settings but i cant do anything hardly in 30 seconds before reboot. Does the same thing in safe mode

im in the same boat after i tried to change my kernel.
its looking like a fd up efs folder. we need a good backup to resotore in twrp to fix efs, or efs repair tool

droseofc said:
Try the general steps but flashing the official firmware or using the one from that thread? The biggest issue currently besides no signal is the rebooting every 30 seconds unless im in download mode or recovery be it twrp or stock. The software version under settings and status shows as unknown as well as sim status and imei status on both lollipop and marshmallow. If i could get it to stop rebooting i could play around in hidden menu or build prop or csc settings but i cant do anything hardly in 30 seconds before reboot. Does the same thing in safe mode
Click to expand...
Click to collapse
Hi are was able to fix your issue I have a phone with the same issue i try almost everything and the only way if I install a international room but no signal and is missing meid in settings
if you have a solution for this the phone is useless please share,

Duplicate post-delete

which modem will give me the best signal/reception? lollipop or MM ?

can you tell me
this modem file working all models like s6 s6edge note5 etc etc... ??????????????????????????
i have lots of pecs for emergency call service problem so please reply me fast if this file is working so my problem is solve

Same problem but different model
Hello, I got the exact same problem but my note it's a different model than yours, is it safe to flash with the file you post, I'm from Mexico and I'm on emergency calls only, the flashing of this file it's done in download mode also right?
Saludos.

Carlos.aat said:
Hello, I got the exact same problem but my note it's a different model than yours, is it safe to flash with the file you post, I'm from Mexico and I'm on emergency calls only, the flashing of this file it's done in download mode also right?
Saludos.
Click to expand...
Click to collapse
No.

Hi , my note 5 was originally N920P(sprint) before I bought it. It was rooted and the model number was changed to N920F (IDK how they did it) . I guess they did that to bypass network lock. Please how can I flash official firmware without relocking the device to sprint? I heard others with the same phone as mine are getting no network reception after flashing official firmware. Thanks

Happened to me. I had no signal after flashing Marshmallow. Reverting back to any lollipop baseband fixed the issue. I did some digging and it turns out there was some provisioning parameters changes done from Lollipop to Marshmallow which was preventing network to work after flashing Marshmallow baseband. The RIL was using the wrong radio technology setting.
I did the following to fix the issue.
1. Dial ##72786#
2. Press Yes to reset the Provisioning Settings to default.
3. Reboot the Phone.
CAUTION: I am not responsible for broken unlocks. I tried this method and my phone was still unlocked. I don't know if it works for everyone without breaking unlock..

Thanks Buddy. It worked.
But I have another phone with the same problem
Will this file and method work for Sprint Galaxy S5?

TravisAntonio said:
Hello, everyone. It's been a long time since I posted, maybe since my S4.
There may be some of you who are not getting signal or just "Emergency Calls Only" after update/upgrade/flash to 6.0 (MM).
There's a simple solution which I found after many and many tries.
Modem: https://www.mediafire.com/?14az40tk2dkd3gw
Step 1. Download the Modem attached.
Step 2. Open Odin, look for the file and put it in CP.
Step 3. Flash it.
Step 4. There's not step 4.
Enjoy your signal.
Click to expand...
Click to collapse
thanks working for me...

fail with me
i flashed with this modem but it doasnt work with me i still have emergency calls only please helps i am verry lost

Recent samsung devices rebooting a/root cf-auto?

I follow a handful of samsung device threads, tab 3, s6, note 5 etc..., and every one of them have had recent issues that cause the phone to have a reboot that occurs a minute or so after booting up that havent been able to fix with reflashing firmwares or anything related.
My note 5 had to be replaced (no biggie) and others are in the process of doing so as well. A possible fix has been posted by one user but im wondering if possibly the cause is from cf autoroot as it appears that everyone or close to that posted having a similar issue mention cf auto rooting prior.
My steps were flash stock lollipop. Flash stock mm. Cf autoroot stock mm and after that my signal bars or area for were gone completely and the phone rebooted within a minute regardless of airplane mode on or anything else i tried. It did not reboot the same while in recovery stock or custom or download mode as those stayed kn as normal.
I know the warnings and such with cf auto root an whatnot but just wanted to make the observation so that if it is the issue it can be acknowledged before more threads appear with this rebooting issue as it is a PITA.

droseofc said:
I follow a handful of samsung device threads, tab 3, s6, note 5 etc..., and every one of them have had recent issues that cause the phone to have a reboot that occurs a minute or so after booting up that havent been able to fix with reflashing firmwares or anything related.
My note 5 had to be replaced (no biggie) and others are in the process of doing so as well. A possible fix has been posted by one user but im wondering if possibly the cause is from cf autoroot as it appears that everyone or close to that posted having a similar issue mention cf auto rooting prior.
My steps were flash stock lollipop. Flash stock mm. Cf autoroot stock mm and after that my signal bars or area for were gone completely and the phone rebooted within a minute regardless of airplane mode on or anything else i tried. It did not reboot the same while in recovery stock or custom or download mode as those stayed kn as normal.
I know the warnings and such with cf auto root an whatnot but just wanted to make the observation so that if it is the issue it can be acknowledged before more threads appear with this rebooting issue as it is a PITA.
Click to expand...
Click to collapse
I did do my best to make it grammar friendly but apparently where i put the tabs and spaces for paragraphs only put the tabs and not the spaces so i giveup on future paragraphing efforts

Well there replacing my battery which i doubt will fix it but when i get another phone im staying away from rooting until this problem get solved . I lost alot of stuff on that device also my next phone will have a sd card or I'm not buying it cloud storage with sprint service =failure
Sent from my SM-N920P using XDA-Developers mobile app

I didn't cf auto root and had the unfixable reboot problem.

Me either i did day one when rolled to 6.0.1 but had odin stock since then only odin twrp then flash supersu2.71.zip.
So im not convinced that cfauto did it now mine is working perfect or better lol. The reboot issue did u pull sim card flash stock. i flashed it but still rebooted any rom it rebooted but i think after that i click repartition in odin with stock tar but then re did it stock tar in odin again . i odined the stock tar into pitfile. then i re odin stock tar after that let it die. im not sure how i fixed it but i did.
---------- Post added at 09:08 PM ---------- Previous post was at 09:03 PM ----------
I also flashed twrp and restored radio and efs back multiple times
---------- Post added at 09:10 PM ---------- Previous post was at 09:08 PM ----------
Once it worked sucker was booting up in 14 or 15 seconds and has seemed better then ever maybe cuz i lost this bad baby for few days while she rebooted idk good luck though

We all did the usual troubleshooting in all my time with the g1,mytouch,htc hd2,samsung vibrant,htc sensation, htc evo,htc 3d,htc evo 4glte, galaxy nexus, galaxy s2, galaxy s3, galaxy s4 , galaxy s5 ,galaxy note 1,2,3,4,5 nexus 6 , lg optimus,lg g2,lg g3, gflex,glex 2, htc max, nexus 5, i bricked several devices and fixed them all. This note 5 problem takes the cake i wasted to much time trying to fix it before i said enough. The security on every device year by year is getting ridiculous no matter what you do anything can be hacked.
Sent from my SM-N920P using XDA-Developers mobile app

I guess one more thing to my rambling.
It happened right after i restored a back up but i swiped to restore i saw that efs was checked i said nooooo but it was to late. I never touch that for the most part. one other time i restored it in 5.1.1 i took 2 or 3 minutes before signal.

Well i helped another he tried everything it was rebooting on any rom. i suggested let it die well his worked after that
IF CONSTANT REBOOTING FLASH STOCK
LET BATTERY DIE COMPLETELY

I retract my observation about autoroot then and apologize for that. I just got the same issue with this replacement phone after flashing skyhigh 3.4 in twrp. I let it die as others say works and it did work but su was gone so flashed su in twrp and then had the same issue. Let it die and now i am running skyhigh 3.4 with the su i flashed with no issue. Leaves only one possibility, seems as if its not skyhigh, not su or autoroot but could it be twrp?

Im using 3.0.2.0 twrp with the theme options flashed to it if that makes a difference but to be specific and possibly narrow it down.

Can someone down grade twrp and find out
Sent from my SM-N920P using XDA-Developers mobile app

Well several on g920p the s6 have had the problem we got twro 3.0.0-1 build by sac23 works newer ones wont boot. i got the tebooting problem for 2 days right after a efs restore.
---------- Post added at 04:01 AM ---------- Previous post was at 03:53 AM ----------
Still its unofficial so this is where them problem starts but maybe somebody needs logs while rebooting nonstop

I cant say its twrp for positive, im just saying in my case, i flashed skyhigh 3.4 in twrp. Had the no signal reboot issue. Let it die. Charged and rebooted and was fixed running skyhigh 3.4. Su was gone tho, so i went to twrp and flashed su, got the same issue.
Let it die, charge reboot and su was installed and everything was fine. The only thing that was the same throughout the problems was twrp. At the same time, twrp successfully flashes with no issues most if not all of the time, its just in this case twrp was used for two different flashes and the same issue occured and a die and reboot displayed both flashed objects running successfully so I would have to point to twrp as it couldnt be skyhigh or supersu and those would be the only 3 possibilities in this case.
I had issues installing the twrp 3.0.2.0 from the twrp.me site, it would bootloop to the recovery is not seandroid enforcing until i flashed a recovery that either worked or flashed stock rom, until i came across tdunhams recovery file listed in his moar mm thread linked note 5 recoveries. Its hard to say its twrp because it works for sure, its just a few times where it hasnt there arent many other things it could be.

Why is my S7 Stuck on the T-Mobile screen / Doesn't work and how do I fix it?

So, I rooted my S7. It worked fine. One day, randomly out of no where it bootlooped (Google play services crashed. I restarted phone and it bootlooped. )
I have not made a single system modification other then rooting it. Didn't mod anything or mess with system files, and I had barely even been using the phone when it happened.
So I unrooted it (The phone still gave me the "Custom" symbol though) and Just now-- It randomly restarted. I didn't restart it. it just did it by itself. And it came into a bootloop. I don't understand why. What can I do to fix this?
MORE SPECIFICALLY: By Bootloop, I mean it stays on the T-Mobile screen and vibrates every minute or so and does not do anything (I even left it alone for ~ 30minutes and it never got past this screen)
Factory resetting the phone fix's it, but I don't want to factory reset my $400 phone every week! I don't understand how I could fix this either.

What method did you use to unroot? Did you flash stock firmware with odin?

sparky2029 said:
What method did you use to unroot? Did you flash stock firmware with odin?
Click to expand...
Click to collapse
All I did pretty much was flash stock s7 firmware. (More specifically boot.img)
Originally couldn't find a stock s7 image then I just used one I already had and it worked fine

EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open

Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Just now noticed wat your problem is sorry for being late so yes to fix the bootloop refladh stock firm and when you go through all the root steps install xposed (yes it's possible it's insane on how they got it to work but it's possible I've done with my self)after getting xposed installed through flash fire go to xposed and get xtouchwiz something it's a blue gear install that And it will set your system status as official
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Here's a quick explanations of wat i think it is it's becuz you've ether heavenly been modding the phone or if your phone status is custom then that's the problem I had with mine after asking around someone gave me the fix i put it in the other comment hope this fixes your issue it worked for me 2 months of no bootloop I switched to 7.0 vzw beta so I lost root

New OS Updates for Galaxy s6

Hello so i have Galaxy S6 that does not have original firmware... surprise surprise..but i have been wondering about something.
Lets say that Samsung makes official android 8.0 oreo for galaxy s6. So how do i upgrade to it because i have custom rom called frankenstein os
...but i also have a twrp made backup of official samsung firmware that i can restore but the reason that i am not using that firmware is that its
really laggy bcs of something, i rooted the phone barely unbricked it and the official firmware is almost unusable to me...ah and yea i don't know
is it going to be able to install the update(android 8 if it comes) without the stock recovery that i also have. I am afraid of flashing stock recovery back because i had that "brick" problem where i could not flash anything through odin not even twrp. And is it possible to flash stock samsung firmware when it comes out from twrp? Like i download it from sammobile and can i just flash it through twrp? And can i flash now android 7.0 (official) from sammobile with twrp bcs odin does not work to me for some reason.
Thanks for your time

Short answer? No.
Lomg answer? You'd have to flash the firmware using Odin. Or wait a bit after it's released as someone should be able to make a flashable version of it (or even better - a flashable debloated deodexed version of it). That all is off course IF it gets released for the S6, which is unlikely, at best.
Best hope is it gets released for a phone that's similar enough to be able to port it, such as the A8 2016 - that's what people are hoping for, currently.
---------- Post added at 03:42 PM ---------- Previous post was at 03:41 PM ----------
Also, you seem to face an error I had. When you flash a firmware using Odin, make sure to go into recovery and clear cache, as well as Dalvik, and then try to start it up.