Hey.
I have noticed an increase in battery draining since I rooted my device. My phone lasts for an hour and a half before it gets down to 30% and that's just messaging on Facebook Messenger and scrolling Facebook itself from 100%. I tried full unroot via SuperSU but it only made my phone reboot loop. I didn't do a traditional root like most do by using custom rooted ROMs, all I did was follow the instructions for a only rooting for root permissions.
That being said however, because I haven't got access to a computer at the moment and because SAMMobile takes 4 hours to download the stock official firmware I can't restore it. - My biggest concern is if I use Flashify or TWRP to restore the original boot thing I'm afraid it'll put my device into an infinite boot loop and break it. I have a file called "G925FXXU5EQBG_G925FVFG5BG_G925FXXU5EQAC_HOME.tar.md5" downloaded but unsure if it's the original stock file or not. My main question is that if I restore the original firmware using an app on my phone (if even possible) will it boot loop?
Related
I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Reroot I had no problems
Sent from my LT28i using xda app-developers app
defsix said:
I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Click to expand...
Click to collapse
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
So do you think I could delete one of the systems?
I will stick it out until the next version is out if it's too much hassle.
Sent from my LT26i using XDA Premium HD app
Check out the all in one tool v5 when it comes out tonight my guess is itll fix ure problem!!
Sent from my LT28i using xda app-developers app
Will try at the wknd.
Sent from my LT26i using XDA Premium HD app
stifilz said:
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
Click to expand...
Click to collapse
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
[email protected] said:
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
Click to expand...
Click to collapse
Use AIO tool. 'Rescue back-door'. Then manually flash the file through recovery. Zip file link in signature and a FAQ including how to flash from recovery.
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
[email protected] said:
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
Click to expand...
Click to collapse
So after a few more days messing with this i'm still stuck. I booted into recovery , performed a factory rest, rebooted and did it again. Then I re-installed a full install of R5 , rebooted, factory reset. When I first boot I have (IRC) 30 apps, powercycle again I have 33 (IRC) apps, it appears I have extra ones that only appear in the vendor directory, again IRC. So rooted both partitions , double booting each time AIO said it was rebooting, I had root on both sides, however certain apps when started on the different partition were losing their settings. So with Root Explorer I decided to do a little trimming on one partition, I deleted the vendor and system folders and the tablet rebooted. So now I have one dead partition and one good. The good one works fine and is rooted, when I reboot it gets stuck in a boot loop at the Sony logo, press and hold the power button for a few secs and it reboots again , apps and settings unaffected.
So how do I have 2 partitions and how do i delete one ?
I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
nuar_y said:
I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
Click to expand...
Click to collapse
I see that so far you have found a way to disable knox AND cripple your Mega...
IMHO the best way to fix this situation is:
1. Download once more your newest firmware I9205XXUCNA3 (e.g. from Sammobile) and flash it by Odin to resolve starting position. Or try to restore your firmware through Kies.
2. Then BEFORE YOU DO SOMETHING read forums to find information how safely root firmware with KNOX. You have to be known so probably your warranty is already void and if not so it will be on the first attempt to root your unit. You are warned... There are some threads about rooting KNOX-ed firmware and even how to come back (partially) to previous build.
BEWARE! Do not attempt to flash older firmware lest you brick your Mega. New bootloader prevent from downgrading and if you try you will have endless bootloop. Upgradindg to newest firmware is one way trip.
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
nuar_y said:
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
Click to expand...
Click to collapse
I am glad you are successful. Sometimes you have to repeat two times, but no more: one for download errors, two for your errors. But if then you are not successful... then you have to look for another solution...
Can I know what rom u are using before updating to stock rom using kies?
Sent from my GT-I9205 using XDA Free mobile app
Hello! Sorry for my panic and sense of urgency, but I'm currently away for school and my lease is ending at the end of the month and I have no way to contact my parents, real estate agents, movers, or anything now. All I have is my phone and computer, and I haven't renewed my internet for the month so it should be shut off any day now as well.
But I was running Lollipop (OC1) and rooted my phone the other day with the terrible KingRoot. I attempted to use this app that was supposed to remove KingRoot and replace it with SuperUser but it only removed KingRoot - nothing else. So I lost root access, but still had all the KingRoot crap on my phone. Today a Verizon update appeared on my phone and I clicked install - I didn't think anything of it because it wasn't a major OS upgrade, just a small patch. Plus I thought it'd help remove KingRoot. Uh oh. I was wrong.
I installed the update, it went into recovery and then attempted to install. next thing I know all I see is a black screen. I tried pulling the battery and rebooting it, but I can't get passed the Samsung logo - it just goes to a black screen (but I believe it's still on, draining battery). If I try to boot into recovery it INSTANTLY starts auto-installing this update, which it of course always fails to do and gives me an error message.
My brother said I need to use 'ADB' but he's busy and can't email me much more information. I'm entirely lost, panicked, and scared! I need my phone working soon. I'm assuming theres no way to 'fix' my phone - so I'm just going to have to suck it up and realize I lost everything (man I wish I saved a lot of people I was texting as contacts *face palm*). What can I do now?
P.S. If I need to install a new ROM or whatnot over this, then can I do so with a pre-rooted Lollipop ROM? That way I don't have to risk using KingRoot ever- ever again. NOTE I NEED ROOT FOR WiFi TETHER! My internet is being shut off very soon, so to get by in the meantime I planned on using my phone and its tether.
No... You need internet access..
BUT... If you backed up everything to the external SD, then you can regain contacts..
Otherwise, Any attempt to fix it won't do anything...
ADB won't work on this phone either...
What you need to do is download a program called Odin, and a OC1 stock tar... That will recover your phone, but you will lose all contacts unless you had the Verizon contact thing...
I had the exact same experience as you yesterday... I had to put my phone in Download mode and start fresh with the Verizon Software Update Assistant. All I really cared about was my pictures, and they were on the external SD card. The other response about using ODIN to go back to OC1 works just as well... Best of luck!
Odin is your friend
Don't panic. You're contacts and other media of a similar nature are usually backed up regularly enough if you don't mess with the default sync settings of your stock rom. We can all agree Kingroot is a terrible way to root because of it's unnecessarily bloated bundle that it installs along with its super user app. To get your phone working you need to 'Odin' back to stock and from there you can root and install a custom rom. However your choices are very finite because of the new SELinux enforcing files on the OC1 build for the Verizon bootloader.
Step 1) Download Odin here ---> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Step 2) Download the stock OC1 Build ROM for the SCH-I545 (Verizon Galaxy S4) here ---> http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-5-0-1-lollipop-oc1-t3174850
Step 3) Once the download has finished (use DownloadThemAll add-on in FireFox to boost download speed) load the tar.md5 file into Odin
using the AP button.
Step 4) Put your phone into download mode and plug it into your computer. Make sure the cables aren't loose and click start in Odin.
Step 5) Wait for the phone to reboot and for the com-slot in Odin to turn green (will say "PASS!!" when complete).
If you use KingRoot to root the phone then I suggest googling how to replace KingRoot with SuperSu and following the tutorial W0lfdroids website here ---> http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Before I start, my phone IS rooted (Rooted with KingRoot 4.4.2)
So as I was trying to put my phone's SELinux from Enforcing to Permissive, i've come across editting the build.prop file successfully, setting 'ro.build.selinux' or whatever it was to 1. Then, that wasn't working, I was told deleting Knox (which I've already uninstalled and deleted all of the apps for it), but the files were still left behind, so it was still there. I grabbed Root Explorer and deleted everything of Knox. The next time I rebooted, my phone was stuck on the Verizon logo screen, got past the Samsung screen fine. So my phone is now bricked from deleting the stupid Knox core files and stuff and I can't find the damn recovery tar/md5 file for it anywhere; I used to have it, but since I've upgraded to Windows 10 a few months earlier, I formatted everything due to unneeded storage being tooken up and lost it in the deletion process. So I ask, does anyone have the recovery file that boots the stock, I remember the file I had what it was named - something like "VRUFND7_i605T0LTEVZW4.4.2_HOME.tar.md5" something like that..including those words I doubt it would be named the same way as this, but PLEASE help me. I need my phone for many purposes and it is the only one I have.
I have hosted the files on my website here and you can get them form the forms below
http://goofwear.com/android/index.p...Samsung Galaxy Note II - I605/Stock/Firmware/
Go Here and download either of the Firmware Files and download the pit file (MAKE SURE YOU LOOK AT WHAT BOXES TO CHECK AND UNCHEK IN ODIN) http://forums.androidcentral.com/ve...note2-return-100-stock-updated-5-12-13-a.html
Unlock your boot loader
http://forum.xda-developers.com/showthread.php?t=2118348
root your phone with ANY other way on XDA besides Kingo Root. Only use Kingo root as a last resort when their is NO root method available for your device.
Also get use the Clockworkmod recovery . I could not get roms to boot or flash property on the TWRP Recovery. I had to Odin back multiple times.
Dreemzx1 said:
Before I start, my phone IS rooted (Rooted with KingRoot 4.4.2)
So as I was trying to put my phone's SELinux from Enforcing to Permissive, i've come across editting the build.prop file successfully, setting 'ro.build.selinux' or whatever it was to 1. Then, that wasn't working, I was told deleting Knox (which I've already uninstalled and deleted all of the apps for it), but the files were still left behind, so it was still there. I grabbed Root Explorer and deleted everything of Knox. The next time I rebooted, my phone was stuck on the Verizon logo screen, got past the Samsung screen fine. So my phone is now bricked from deleting the stupid Knox core files and stuff and I can't find the damn recovery tar/md5 file for it anywhere; I used to have it, but since I've upgraded to Windows 10 a few months earlier, I formatted everything due to unneeded storage being tooken up and lost it in the deletion process. So I ask, does anyone have the recovery file that boots the stock, I remember the file I had what it was named - something like "VRUFND7_i605T0LTEVZW4.4.2_HOME.tar.md5" something like that..including those words I doubt it would be named the same way as this, but PLEASE help me. I need my phone for many purposes and it is the only one I have.
Click to expand...
Click to collapse
If you were previously on the stock Verizon firmware 4.4.2 ND7, (which I'm assuming you were), then you have a phone with a locked bootloader that has no current method to unlock it. Adam Outler's Back Atcha Verizon and Casual won't work to unlock the bootloader.
You also cannot downgrade the phone to a previous firmware version because of the unlockable bootloader. Regular Custom recoveries such as CWM will not work either because of the locked bootloader. The only custom recovery that currently works on the locked 4.4.2 bootloader is Safestrap, which is a modified version of TWRP.
If you were previously on stock 4.4.2 ND7 before everything got messed up, then you can only restore the phone back to stock 4.4.2. You can find the stock 4.4.2 firmware at Sammobile.com. It costs nothing to download it from Sammobile, but you will have to register which is free.
If you can still boot the phone into Odin mode (i.e. Volume down+home button+power button), then you should hopefully be able to use Odin to restore the phone back to stock 4.4.2 firmware to get it working again.
Recognized XDA Contributor Droidstyle put together a detailed guide on how to restore the phone back to stock firmware. See the guide under section 1b here: http://forum.xda-developers.com/showthread.php?p=34891181
The guide is still accurate for the most part, except you'll need to restore the phone back to the 4.4.2 Stock firmware (assuming that's what firmware version you were on previously), which you'll have to get from Sammobile since it's not available through Droidstyle's guide. Also, if you use the newer version of Odin like version 3.0.9, then you have to load the phone's firmware into the AP slot, (not the PDA slot which is mentioned in Droidstyle's guide.... the PDA slot is what used to be used in ODIN 3.0.7 and older Odin versions).
Hi guys, new to this forum and new to playing around with Android Phones. I have a Samsung Galaxy Note 5 and was using it to test my ability to root a device before getting an S8 when they launch. The reason behind this is I play Pokemon Go and use the mock locations application which the March Android security update blocks.
I intended on installing TWRP, rooting with Magisk, hiding the root and install the mock location app as a system app using Link2SD. I downloaded TWRP and used Odin to flash it to my phone. However I think I did something wrong as my phone was stuck on the Samsung logo endlessly.
Now I can boot my phone into TWRP but no matter what I do I cannot get back into my Android system. I have hit a few reset and delete buttons so I am assuming my system is well and truly screwed. I am not fussed about losing the data on the phone, but just want to be able to use it again.
I think the mistake I made was not unchecking auto-reboot and installing the root at the same time as TWRP which according to a thread I read you have to do on Samsung phones?
Is there a way I can re-load a stock ROM using TWRP? Or is there a way I can wipe everything including TWRP and start again? At the moment I have a pretty useless phone. I would like to stay with a stock ROM and am avoiding using a ROM that is already rooted as I want to use the rooting method shown above to conceal the root (the game won't open on a rooted phone).
Please help!