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.
Related
Q&A for [ROM][4.4.4][AOSPA] ParanoidAndroid 4.6-beta4 | Skyrocket
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
"Security" crashes while triying to change screenlock settings
HTML:
In: [ROM][4.4.4][AOSPA] ParanoidAndroid 4.6-beta4 "Security" crashes while triying to change screenlock settings.
I just want to disable it. ¿Someone knows how to do so by coding?
Thanks!
he;lp
I can't seem to get this ROM to flash. The flash process fails quickly with a non-descript error message:
error executing update binary in zip
error flashing zip
Click to expand...
Click to collapse
I'm using TWRP 2.8.1.0 and I tried flashing the latest nightly as well as the stable version. I verified the MD5 signature after copying the .zip to my SD card. I also did a full wipe with TWRP.
My phone is the i727R with Gingerbread 2.3.5. Do I need to update to the latest official 4.x firmware from Rogers before I try to flash with AOSPA?
Any other suggestions or hints? This is my first time trying to flash a custom ROM, so I'm probably doing something wrong.
Figured it out, didn't have the latest radio installed. Might want to add that to the instructions for noobs like me. It's easy to overlook because the note regarding the firmware is under the "contributors" heading, separate from the basic instructions.
camera doesn't work
Camera is not working for me, but everything else is fine. And pretty darn smooth!
Issue installing
I am attempting to install this using CWM and the installation of the ROM goes perfectly but then when I go to install the GApps, I keep getting the insufficient space error. I have tried Mini, Micro and Nano as well as reformatted the internal memory. Thoughts? Sorry for the ignorant post.
---------- Post added at 05:55 PM ---------- Previous post was at 05:49 PM ----------
harrisd23 said:
I am attempting to install this using CWM and the installation of the ROM goes perfectly but then when I go to install the GApps, I keep getting the insufficient space error. I have tried Mini, Micro and Nano as well as reformatted the internal memory. Thoughts? Sorry for the ignorant post.
Click to expand...
Click to collapse
To be clear, I am talking about the 5.0.2 ROM not the 4.4.4 ROM. The 5.0 thread would not let me post there and redirected me here for some reason.
harrisd23 said:
I am attempting to install this using CWM and the installation of the ROM goes perfectly but then when I go to install the GApps, I keep getting the insufficient space error. I have tried Mini, Micro and Nano as well as reformatted the internal memory. Thoughts? Sorry for the ignorant post.
---------- Post added at 05:55 PM ---------- Previous post was at 05:49 PM ----------
To be clear, I am talking about the 5.0.2 ROM not the 4.4.4 ROM. The 5.0 thread would not let me post there and redirected me here for some reason.
Click to expand...
Click to collapse
I'm not sure if CWM is compatible with the GApps. I recommend using TWRP instead.
But I have used CWM for GApps for all my ROMs so far and it hasn't been an issue. Why would this be different. My understanding is that it is just a space issue so I am wanting to know if there is a way to get this space issue resolved when even the smallest GApps was still too large (supposedly).
---------- Post added at 02:17 PM ---------- Previous post was at 01:22 PM ----------
harrisd23 said:
But I have used CWM for GApps for all my ROMs so far and it hasn't been an issue. Why would this be different. My understanding is that it is just a space issue so I am wanting to know if there is a way to get this space issue resolved when even the smallest GApps was still too large (supposedly).
Click to expand...
Click to collapse
Also I am now just running Cyanogenmod 5.0 with the exact same GApps and that worked fine. Thoughts?
Different recovery
Why did this rom install cyanogen recovery, this recovery sucks and I cant get to any of my backed up roms because it doesnt give me an option, how the hell do I get back to philz?
Trouble updating
I installed the 1/16/2015 version (PA 5.02) plus nano gapps. Most things seemed to work well, and I like the look and feel, but two or three times I have experienced periods where the battery drains even though connected to a charger. This morning, for example, the phone had been on the charger all night and was fully charged. Without disconnecting it from the charger, I checked my email and then put the phone back down. An hour or so later, the battery showed low 90's percent, even though it showed that it still was plugged in.
Yesterday I tried to update to the 2/2/2015 version. After making a backup with TWRP, I installed the 2/2 zip. I have flashed several ROMS, so I am not a complete noob, but I have never done a zip upgrade without factory reset. The upgrade seemed to succeed, but after booting, I had no gapps and my google accounts were missing. I then tried reflashing the same gapps and the systemUI fix. That got my apps back, more or less, but my google accounts still were missing and my home screen layouts all were lost. I then reverted to my pre-upgrade nandroid backup and tried again, by installing the 2/2 ROM upgrade zip, the gapps, and the systemUI fix all without rebooting in between. As before, after rebooting, my home screens were gone and (I think) my google accounts were gone. (By the way, I use the Google Launcher.)
Is upgrading from the 1/16 to 2/2 supposed to require reinstallation of gapps and adding back of accounts, home screen setups, etc? If it is then such an upgrade is almost as much hassle as a complete, clean install. Can someone tell me how this is supposed to work?
I installed the Lollipop rom (and the UI patch) and am still having "Can't connect to camera" issues. occasionally, rebooting the phone helps, but then if I do something like switch from the back camera to the front, it will stop working again.
Sealy64 said:
I installed the 1/16/2015 version (PA 5.02) plus nano gapps. Most things seemed to work well, and I like the look and feel, but two or three times I have experienced periods where the battery drains even though connected to a charger. This morning, for example, the phone had been on the charger all night and was fully charged. Without disconnecting it from the charger, I checked my email and then put the phone back down. An hour or so later, the battery showed low 90's percent, even though it showed that it still was plugged in.
Yesterday I tried to update to the 2/2/2015 version. After making a backup with TWRP, I installed the 2/2 zip. I have flashed several ROMS, so I am not a complete noob, but I have never done a zip upgrade without factory reset. The upgrade seemed to succeed, but after booting, I had no gapps and my google accounts were missing. I then tried reflashing the same gapps and the systemUI fix. That got my apps back, more or less, but my google accounts still were missing and my home screen layouts all were lost. I then reverted to my pre-upgrade nandroid backup and tried again, by installing the 2/2 ROM upgrade zip, the gapps, and the systemUI fix all without rebooting in between. As before, after rebooting, my home screens were gone and (I think) my google accounts were gone. (By the way, I use the Google Launcher.)
Is upgrading from the 1/16 to 2/2 supposed to require reinstallation of gapps and adding back of accounts, home screen setups, etc? If it is then such an upgrade is almost as much hassle as a complete, clean install. Can someone tell me how this is supposed to work?
Click to expand...
Click to collapse
There are issues with the gapps backup script, so the gapps package should be flashed with every ROM update. The loss of gapps most likely caused your accounts and home screen to be removed.
morallyobjected said:
I installed the Lollipop rom (and the UI patch) and am still having "Can't connect to camera" issues. occasionally, rebooting the phone helps, but then if I do something like switch from the back camera to the front, it will stop working again.
Click to expand...
Click to collapse
This should only happen when using the front facing camera. This will be fixed next update.
Bummer
Losing home screens and accounts every time an update is flashed is a bummer. Putting everything back (accounts, home screens, Power Toggles settings, ...) makes me hesitate to try an update very often.
You say the problem is with gapps. Does this same problem occur with all flavors of ROMs and all flavors of gapps? I ask because my previous experience with installing ROMs has been installation of new ROMs, not updates to one already installed.
Incorrect information in battery monitor - PA 5
I've been using (and generally liking) the PA 5 for several weeks. I have noted, however, that the breakdown of battery usage, as reported by the OS, seems inaccurate. As just one example, yesterday, I started a 15-minute call shortly after unplugging my phone from the charger, with a full battery. At the end of the call, I was down to about 90% battery. That seems reasonable to me, based on past experience. The battery monitor said almost all of my battery consumption was for Cell Standby, though, with only a little consumption assigned to actual phone use. I've seen some other examples where the usage breakdown did not seem right, although I did not document them and do not recall exact details.
Am I correct that this is incorrect behavior? Are others experiencing this (or does anyone pay attention to it), either on this ROM or on other ROMs?
i have the problen in de boot reset
friends have a big problem and installed the rom 5.0.2 and it works wonders but when you restart the system displays the logo of sangsung and giving in black screen help me?
I did the steps correctly install the rom and then gapps and finally the root
sorry for my english..XD
s2 ky i727
cwm6.0.3.3touch_skyrocket
gapps --pa_gapps-modular-micro-5.0.1-20150315-signed
[ROM][5.0.2][AOSPA] ParanoidAndroid 5.0-alpha1 Skyrocket [02-19-15]
jorgx said:
I did the steps correctly install the rom and then gapps and finally the root
sorry for my english..XD
s2 ky i727
cwm6.0.3.3touch_skyrocket
gapps --pa_gapps-modular-micro-5.0.1-20150315-signed
[ROM][5.0.2][AOSPA] ParanoidAndroid 5.0-alpha1 Skyrocket [02-19-15]
Click to expand...
Click to collapse
u didnt follow the steps/instructions. read them again.
wrong recovery
dont root
what is s2 ky i727
should be sgh-i727
vincom said:
u didnt follow the steps/instructions. read them again.
wrong recovery
dont root
what is s2 ky i727
should be sgh-i727
Click to expand...
Click to collapse
excuse my model is s2 sgh-i727 model XD
rom behaved extremely stable the only mistake was that hangs on reboot goes black
you recommend I do?
that recobery should I use?
the gapps and rom are well take?
It is the first time I install this rom.....thank you for your help XD
jorgx said:
excuse my model is s2 sgh-i727 model XD
rom behaved extremely stable the only mistake was that hangs on reboot goes black
you recommend I do?
that recobery should I use?
the gapps and rom are well take?
It is the first time I install this rom.....thank you for your help XD
Click to expand...
Click to collapse
i could tell u but for new users u need to start slow, read, start here READ THIS B4 POSTING | THE MOST Common Questions Answered HERE
Sweep2wake feature
Sir, I have problem with Sweep2wake features. when enabled, after i locked my device. the screen wakes when i press either one of the dedicated buttons. even when i enabled the first & last button to wake. hope you can fix this issue. thank you & more power.
Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man
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
Every time I install a rom, the device does not want to boot up. It loads the Samsung J7 logo, then goes black. Waiting for a long time does not work. I've waited for an hour to no avail. I have tried Alpha Centauri, Nameless 3.5, SyneXOS and all do not boot up. The aroma installer loads up correctly in TWRP. I have tried downgrading TWRP, wiping phone clean before installs, different downloads, and even reflashing stock FW and reinstalling TWRP. my phone's baseband version is J700FXXU4AQD1, just in case someone asks for it. I have yet to find out a way to get a log of the system while booting, as it may help uncover why so. To my knowledge, this phone may be SIM locked, but I have yet to confirm. Feel free to ask for any more necessary info. Thanks! <3
I have the same model fon and all those roms boot for me.
Maybe use a fresh flash disk - only ROM zip no other files / folders, and do a FULL wipe before flashing.
As usual keep a backup of EFS and Radio folders.
Latest TWRP is best. Battery > 90%
Sent from my SM-J700F using Tapatalk
Battery dead? Or too weak to get beyond splash?
I did something awhile back (phone was unrooted and 100% stock) and it refused to charge or to boot beyond Samsung splash screen, and of course the battery was drained, so ZERO way to get phone to turn on as it'd instantly shut down. Happened after doing a win7 windows optional update adding Samsung usb drivers or something. Phone was charging via usb I sometimes have connected to the PC, hence windows update detected the phone and suggest the driver. I don't know exactly what wrong, but it'd loop constantly when trying to charge. Pulling the battery and reinserting fixed it.
Also, fwiw, I just had to do a factory firmware reinstall on a rooted J7 after mistakenly turning off the developer options. It was fully locked, including recovery. I used the giant 1.4gb zip from Samsung (had to join the SamMobile BS to get the file) that ballooned to 2.5gb unpacked, that was exactly for my phone. After flashing that with most recent Odin, phone is back to it's pre-rooted state, replete with bloatware. But all files (pics, etc.) are still there. Maybe try that if battery isn't at fault?
Yes, I too have experienced that stupid "non charging" charging on the usb port.
@aMega329 make sure your fon is not connected to a pc / laptop as you flash ?
Sent from my SM-J700F using Tapatalk
Ok. thank you for the tips. I am now going to try flashing the rom now. I will update soon.
UPDATE: nope. no avail. Fully wiped, battery at 95% at start of flash. Not plugged in to a charger nor a PC. Formatted data partition after flash. Reflashed 2 times. Guess i'm SOL for custom roms. :'( Stock works tho.
Hmmm ..... , I thought just wiping the data partition is enough. Why are you formatting?
I don't format ever!
---------- Post added at 03:53 PM ---------- Previous post was at 03:44 PM ----------
Are you sure J700FXXU4AQD1 is marshmallow 6.01? https://shell.boxwares.com/Download.aspx?L=1250
You need to be on MM first before installing these roms.
I'm on 5.1.1... hmm. I'll try updating f/w to 6.0.1 first then doing everything again. Thank you for the idea though. I'll get back soon after i flashed 6.0.1. Man, it'll take forever to download that.
www.updato.com is your friend for speedy firmware downloads.
Sent from my SM-C900F using Tapatalk
Okay. So guys, I finally got Alpha Centauri to boot. What I did was i downloaded a MM firmware for a J700F in another country, then flashed twrp and the ROM. Thank you guys. I guess our telcos just suck for delivering OTA's to our devices.
For people who have this problem, make sure you are on MM firmware first. If you can't find MM firmware for your device, such as my case, just use firmware from another version. It works for me, but if you doubt it, it's worth giving it a shot. I used J700FXXU4BQI2. Luckily, my Wifi, BT, and mobile data still work nicely.
Congs!
Hi, I am not for miller with everything and I am concerned about what I did.
I followed instructions to install Android 10 on my S6 and when it failed
I got into a panic and found this download CF-Auto-Root-zeroflte-zerofltexx-smg920f.zip
and not paying attention to 920F I installed it using Odin and my phone worked again
but the screen was inverted to the touch screen and on this forum, I found by typing in a sequence of numbers on the keypad
I inverted the touch screen back to be able to use the phone again.
few days later I tried again...
I then installed TWRP and EvolutionX_4.1.69_zerofltexx-10.0-20200331-0232-OFFICIAL Samsung S6 Firmware
and everything went to plan but I am finding my phone to be slower than before, about a 2 second delay to open things and somethings like
opening the camera can take a long time and sometimes it hangs and I need to close the App and try again & the flash only works if I tap to focus first.
My question is should I change my phone back to 920i or is my phone now working as a 920F perfectly fine?
And if so would anyone know where I can find the CF Root zerofltexx sm-g920i download I need?
I have searched and searched and can only find a full factory firmware of 1.88Gb but the file I used "CF-Auto-Root-zeroflte-zerofltexx-smg920f.zip" is only 33.4Mb
I feel I need to find this 920i download to correct my phone back to how it was. Or like I said should I not be worried about it now being 920F?
Thanks
question here is does it work correctly like this? you cannot fix something that is not broken
---------- Post added at 09:11 PM ---------- Previous post was at 09:03 PM ----------
in all seriousness, those issues sound pretty experience-effecting, if i were you i would grab a version of odin and the latest stock rom for g920I, flash stock and eventually get yourself set up with twrp and a recent rom which works with magisk.
i do not see any need for cf-autoroot anywhere in my suggestion, but for the sake of information both cf-autoroot and stock roms should be obtainable on firmware.mobi (and if the download seems to be cruelly slow, this little tool used to be able to get much faster speeds for stock roms but I am not sure if this is still the case anno 2020.)