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.
Related
I recently bought lg optimus net p690. It was running very good. I rooted it 3-4 days ago. There was no problem after rooting. It was running the same good. But while using wifi I ran the "software update" from phone. It downloaded an 18MB file and then updated phone and restarted. After that my phone has become very laggy. It runs slowly. When I slide to change homescreens, they change very slowly. applications too are laggy now. sometimes they crash...
now I want that previous firmware that was running good.
I tried to reset my phone (settings>privacy>erase) but nothing improved (my apps got deleted ).
I dont remember what was the previous firmware version or any thing.. but this is what is displays
Android version 2.3.4
Software version v10e-Jan-06-2012
How do I roll back to the previous version of firmware.. pls help!!
Only death can not be fixed.
How do you know that you downloaded a new fimware or just some application updates?
Did you take note of the software version? (Under Settings/About/Software).
Did it give you any warning about losing your Apps? (Titanium Back-Up is for backing-up Apps).
You can not "roll-back" firmware if you did not do a ROM (also called nandroid) back-up first...
But don't dispair, because If a ROM is not working for you, wether it is stock (Manufacturer) or not, you can get something better here!
Check this post out:
http://forum.xda-developers.com/showthread.php?t=1388831
Cheers, and don't despair, rooting is just the first step to a long and fun path!
BTW, you might have to root it again, but you already know how to.
---------- Post added at 08:12 AM ---------- Previous post was at 08:08 AM ----------
Opps.... Forgot to ask... Did you do a "reset" (Hold Power down and choose reset phone)? A simple reset can solve A LOT of things, better than just pulling the battery out, so try that first and let us know what happened.
Again, you have to ENJOY getting into phones. You will learn a lot while failing and trying again!
i did reset from phone settings. not a hard reset.
it displayed "updating firmware" during the update process.
where can i get custom roms for lg p690? i dont know how to install them. pls help
jn2771 said:
I recently bought lg optimus net p690. It was running very good. I rooted it 3-4 days ago. There was no problem after rooting. It was running the same good. But while using wifi I ran the "software update" from phone. It downloaded an 18MB file and then updated phone and restarted. After that my phone has become very laggy. It runs slowly. When I slide to change homescreens, they change very slowly. applications too are laggy now. sometimes they crash...
now I want that previous firmware that was running good.
I tried to reset my phone (settings>privacy>erase) but nothing improved (my apps got deleted ).
I dont remember what was the previous firmware version or any thing.. but this is what is displays
Android version 2.3.4
Software version v10e-Jan-06-2012
How do I roll back to the previous version of firmware.. pls help!!
Click to expand...
Click to collapse
Hi what country version is your phone?
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.
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.)