I bought the S5 when it first came out and subsequently used towelroot, as soon as it was available. It's been great for customization and extended functionality through the years. Now, however, i have slowly been experiencing more and more issues with this current setup...i.e. some functions have stopped working and many apps no longer work with the kitkat andoid version. Anyway, I am looking for a way to upgrade to marshmallow, or even lollipop, to be able to use apps...and hopefully some ui functionality returns with a reset during the process.
Warning: I have never used odin or flashed roms or anything to that level but i am willing to learn with some good direction.
Current setup:
SM-G900V, Android 4.4.2, Kernal 3.4.0, Build KOT49H.G900VVRU1ANCG, eMMC 15****
If it matters, I also use SuperSU, Xposed.
Not sure what other info would be helpful to assist me, but feel free to ask.
Also lately it can get stuck in a boot loop when rebooting. I'm afraid one day i will be unable to get it to boot up. additionally, it was hit or miss on reboots previously, but now i am unable to get the phone to recognize the SD card. Maybe i should unroot and hard reset, then reroot. Any suggestions regarding that approach? I vaguely remember something about having to undo all the changes made before unrooting.
Edit: All works fine currently, but hit or miss on reboots.
Related
Hey guys, been a long time lurker here and just encountered my first issue, so made an account to hopefully get some advice.
I received the note 10.1 8010 (UK) as a gift for Christmas. I was disappointed to see it was running 4.0, when devices like the Nexus 7 are already on 4.2. And Germany had the 4.1 update for over a month. Samsung as always refuse to give a solid answer.
I followed a guide to install the German 4.1.1 update. I first installed the German version of ICS via Odin. I then applied the update.zip from here:
HTML:
d-h.st/lLB
Prior to this, I rooted the device, but I believe the above process removed the root anyway.
After my device rebooted, the S Pen isn't working at all. It recognises when I take the pen out, but I cannot use it. It doesn't do a thing. I've read about 1,000 forum threads and cannot find an answer, as to how I can get it working again.
I tried deleting cache and user data, then reapplying the update.zip to no avail.
When I boot up in to recovery mode, it does come up with a message about CSC and then the little drop falls over and I have the usual options.
Any idea what I need to do, to get my S Pen working again? Or what I've done wrong?
Many thanks
This is how I rooted the device.
HTML:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
I have a feeling this is the "root" of the issue. I'm not sure how to remove it.
I know previously I wasn't able to change my CSC via CSC switcher, but I am now.
So I guess installing the German ICS and then update.zip, hasn't completely undone whatever rooting it above did.
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Tehkseven said:
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Click to expand...
Click to collapse
This a pretty bummer situation. Sorry you're dealing with it.
I find this interesting, as I followed the exact same procedure to root as you. I haven't experienced any pen issues though.
Could it be the 4.1 you flashed?
This is one of my fears too, so I really hope this can be solved.
I finally managed it.
I downloaded a different German ICS from a different guide and this time it worked no problems.
The one that worked, had a file name: N8010XXALI3_N8010OXAALI3_DBT
Update.zip worked first time after I installed the above ICS.
Hope that helps.
In an attempt to deal with massive instability I was able to upgrade from Samsung Stock to SlimKat 4.4.4r1. The instability problems remain but now I can't install apps. I have tried to flash to Carbon ROM but that doesn't take.
Curiously, all of the indications are that the apps and ROMs are installing but they in fact they actually don't.
The device doesn't even stay on long enough for me to alter a Setting, it trips over in a matter of seconds and reboots. Each time, I get the error message “Unfortunately, The process android.process.media has stopped”.
Could this be the Brick Bug manifesting itself? Perhaps if I repair the PIT that would fix it? Luckily I can access TWRP 2.7.0.0 recovery, I have tried to upgrade to TWRP 2.8.0.0 but that has failed also.
Any suggestions would be welcome
Hi, I would like to thank all those who took the time to read my description. Clearly it has you flummoxed too.:laugh:
In the meantime, I tried flashing Stock ROM but no joy and then I tried repairing the PIT, no joy there also.
My options now are either to ask Samsung to take a look or else wait for a functioning Tab with a broken screen to come along. My Tab is in superb condition and it would be a shame to let it go without at least making another attempt at rescue.
Hey community,
after updating my 5.0 LTE 32 Shield Tablet some month ago and rooting it, I came to the conclusion that I don't really need root, but would like to continue receiving OTAs and have a device that just works.
Prio1:
Have a tablet with the latest updates installed.
Prio2:
As 1, but rooted.
I have made a apps+sysapps backup with Titanium.
What do you recommend as the next step?
Thank you very much.
All the best, Esshahn
Some additions:
1. I noticed I'm actually having 5.0 on my Shield. It's the 5.0.1 update plus the nVidia stuff that comes up all the time in the notification center.
I really just want to undo all root and whatnot actions and have a right out of the box experience on my Shield. I already did some stupid stuff (factory reset) and therefore lost my personal data anyway, so there's nothing to lose.
I noticed this forum isn't really active. If anyone doesn't know the answer, but could point me to the right forum for help that would be nice too.
Thank you
flash the full OTA through recovery: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
then reinstall supersu through recovery, no factory reset needed
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Esshahn said:
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Click to expand...
Click to collapse
you can flash the full OTA through TWRP or CWM, no idea why it won't work with stock recovery though
the update supposedly fixes the graphics glitches that appear in various apps on update 2.1, that might be a good reason to update
Thank you!
Actually, since I didn't have CWM installed anymore, I just sideloaded the latest OTA, which worked nice.
Hello all, I am relatively new to the android rooting scene. I have looked into it before but always became discouraged by the amount of different informaton from different sources. I am a little bit familiar with flashing processes as I used to install CFW onto Sony PSP and PS3 devices. However there's a lot of new terms that I am soaking in and trying to figure out what it all means when it comes to phone rooting. I am currently using a Sprint Galaxy S5 Sport running Lollipop 5.0, with build number, "LRX21T.PVPU2BOH1" and Kernel "3.4.0-4445742 August 6, 2015". I've been looking around and every time I think I find a reliable source for rooting I see a disclaimer saying only works with certain build numbers, and mine doesn't seem to be any of the builds I have seen. A Google search of my build brings a total of 5 searches wit no information regarding it. Anyways I am looking to successfully root my device, install a working recovery mode, and if possible, install a ROM. I have searched through threads and scrounge up some information about the SM-G860P but not enough for me to go through with the process with 100% certainty of success. I also hope that this thread can be useful to other SM-G860P users and a one stop shop for all the files needed to safely root, backup, and restore files. Basically, I know it can be rooted using Odin and CFAR on Lollipop 5.0. But the steps after that I am unsure. Do I install TWRP, CRM, what ROMS can I install, what kernel do I need. Thanks in advance to any developers or members who can provide all the proper links to attain my goal.
I have a very similar build. I have successfully put on root, and CWM recovery, but, any attempts at custom roms have failed (assuming due to kernel), and I am unable to get tethering working, despite having root.
Followed http://forum.xda-developers.com/sprint-galaxy-s5/development/recovery-cwm-s5-sport-sm-g680p-t2907945 for recovery.
I rooted following something like: http://www.android.gs/root-sprint-galaxy-s5-on-android-5-0-lollipop-os/. The key was using the auto root, then flashing the update via CWM. Had to make sure CWM was installed, as flashing using stock recovery caused issues.
Tried to flash CM12 from:
http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-adulterated-cm12-5-0-2-t2987665
But ended up in a boot loop.
I'm also scared to put xposed framework on, since most saying need to use a custom rom or else phone will bootloop.
Using most of the methods to tether, (like adb settings global or sqlite), tether_dun_required keeps resetting back to 1 after turning on tethering, so, I still haven't found a solution to that. I'd love to hear from anyone who's got tethering working on SM-G860P with lollipop.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!