Hello all. I'm a computer science student and aspiring android developer. I'm planning on making a role playing game inspired by legend of zelda using openGL for Java but that's a topic for a different thread. My rooted phone got ambushed by Verizons auto-update and after a few days of failing, I ended up restoring it back to factory settings and finally the phone is working reliably and well (I hope). Anyway, my question is this:
I used ADB when rooting my phone months ago but have not even thought about it since. When I was going through the recent Verizon update debacle, I tried to flash some ROMS to no avail. When I was trying to set it back to the stock ROM so that I could get the update, I kept getting a signature verification error in clockwork mod. Did I need to be doing that update in ADB, pushing the update instead of just placing the file on the SD card?
Related
I had browsed this forum for awhile and was having major issues with AT&T because my phone, as it sat in the eyes of ATT, decided that I needed to be on towers in another county which completely rendered reaching me by land line impossible and my service was such garbage, that I went through five phone numbers in as many phones. My iPhone 4 was screwed, I got a 1st run Nokia Lumina Windows Phone, but the case and windows 8 killed it for me (you had antennae right where you'd normally rest your fingers and so talking on it was a chore. I decided to get another iphone, and another, all met with failure. I stumbled onto these forums one day and discovered the word "root." My iphone was again giving me trouble and my wifes android seemed to do more....way more.
So I'm on my way home with my first android- a cheap motorola atrix HD. When they finally fixed my tower issue I was on my fifth number and I had read on these forums about root. So I get home around Christmas, and promptly rooted my atrix without knowing anything and figured I would learn as I went. I used the motochopper root by djrbliss and Dan Rosenthal (I think) with the fix bootloader screen. I figured I would learn half assed and learn as I go. I download TIBU, and proceeded to brick my phone. I got verification at customer care that the atrix may have been modified, and if it wasnt defective, swap it at the store.
TIBU Brick
Ran on 70 apps total. Removed the wrong one, Brick.
Rooted and botched something stupid, BRICK.
Tried to flash Cyanogenmod. Brick.
Flashed Cyanogenmod and thought I didn't do it right: Grew Frustrated and formatted the phone. ( I was getting as many replacements as I wanted and my wife continued to get irritated with my new hobby which she still hates.
Take my hard bricked HD to ATT store just to find out that I am eligible for the next program.
I shied away from rooting, Got rid of the mega and then got a Galaxy S4. That fever came right back and the next thing I know I am reading, retaining and absorbing as I bricked my S4 four times- twice by not paying attention and twice by not understanding safestrap recovery. The fever of modding finnally got me off of my rear when the guy at best buy reflashed my s4 for the second time and told me about RSD Lite. I go, download RSD Lite, Install my motorola drivers, Install my Operating System via sideload, download CWM recovery, flash CM 10x.x and forget my gapps...no worries, as I had discovered goo.im and f-droid and a few other places where I just found the correct jb gapps moving up from ICS obviously. I then hard brick the Atrix HD and I reinstalled my OS, got the anysoft keyboard from f-droid (the motorola keyboard kept dying) and I flash CM 10 and the JB gapps and bam, I feel like i'm no longer a noob. I was gone for a few months when I did all of this and as soon as I got home, I bought my brothers note 2 which I promptly rooted using cf autoroot and odin and then I flashed the Pacman Rom Stable 4.3. I experienced a soft brick moving up to kit-kat and unstable nightlies of Pacrom, but I moved everything to my SD card and rom installer still had my 4.3 gapps, and stable 4.3 pac rom. I was short on money and had to get a loan on the note 2 which I m getting back.
Now, I'm staring at my S4 for weeks...thinking "god I hate this stupid thing because it has no root on NC1.
Finally, yesterday, I found the towelroot apk and I rooted my i337 NC1. I set up the phone in a few moments, hooked up the proper wanam modules, and I tried with no success to put CWM Philz touch recovery. I was almost resigned to just using the apex launcher but I couldn't stay away from pushing myself to the limit and finally installing safestrap and a touchwhiz rom. So tonight, I finally installed safestrap after reading the steps to get version 3.72 running. Now I was trying to find a compatible touchwhiz based rom that suited me because I finally safestrapped my s4 and ran a backup to my SD, followed by a full wipe (excluding the SD card) and I went right here to read more (on NC1 get the new ODEXED version and I flashed fine without odin, and not rebooting into DL mode, and am now running the Venom v3.02 Safe Strap rom on my S4 like a boss.
Now for the clincher if you're still reading...I don't even know linux, let alone how to use a terminal emulator but for some strange reason, I now know what to do and what not to do to brick a device, and most importantly of all,
super noobs take note:
I FOLLOW THE DIRECTIONS EXACTLY.
I know little to nothing regarding the finer workings of phones (I now know better than to try to mess with things I know nothing about) but I paid attention.
And the payoff is being able to do this to almost any device...but now I am going to read up more because I want to build a nasty rom that gives the user so much access that it borders on criminally sick.
In short, the moral is to PAY ATTENTION. KNOW YOUR LIMITATIONS. FOLLOW INSTRUCTIONS.
Shout out here:
http://forum.xda-developers.com/showthread.php?t=2447482
And Here:
http://forum.xda-developers.com/showthread.php?t=2447482&page=109
Mad props for the simple instruction. I'm gonna go play with my.....new touchwhiz ROM on my S4.
Well I posted this in general - but I didn't get a reply - and I'm really desperate.
When it comes to mobile platforms I'm more or less as green as they come - so forgive my ignorance regarding... Everything
I recently misplaced my beloved Nexus 4's flipcase. The day it went missing, I managed to stumble and drop my phone a distance onto tiles . It landed at such an awkward angle that the screen not only cracked but pretty much shattered - killing what I believe is known as the digitizer with it. It won't respond to touch.
Distraught I took up my dad's old Galaxy S3 - which was only cracked and a bit eaten (puppies). I went straight into using it and due to a demanding schedule I didn't have time to recover any of the data of the N4 - which I don't know how to do anyway. I quickly learn that I hate Touchwiz and the lack of personal details wakens me to how reliant I am on my phone.
So I set aside some time to get root - load a custom ROM (pa) - and transfer all my data from the N4 to the S3. The first difficulties appear when the S3 rejects towelroot. I install the towelroot apk from the official website and run it. Towelroot tells me it's currently an unsupported device. I google the model number (i9300) and apparently it works with Towelroot. Weird - I guess I'll do it manually.
So I install odin and download what I need and get the drivers for the S3 working and get root. It works without a hitch (I think until later ). Next I look into how to get a ROM on my phone. This happens: http://forum.xda-developers.com/para...4/post54744770 (that's my post btw so it's the exact scenario). I will say that while I was going through this issue I tried many things to try and get rid of the error - I played with CWM a lot - tried to update it - updating failed with unknown errors. - I tried to flash my recovery - it couldn't flash my recovery. Earlier I had tried to install the CWM recovery on it's own from the play store (again - total noob) I only got related versions of CWM from 2011-2012. All of these problems were pretty confusing - and eventually due to the generic error about not being able to flash my recovery I had no idea how to proceed so I did as advised in the thread above and installed Flashify.
Flashify told me I had root, but that it couldn't get access to SuperSU - and to delete SuperSUs memory of Flashify. I went to SuperSU and SuperSU told me that it needed to update my binaries (I don't even know what my binaries are?!). I tell it it can go ahead and it just says "installation failed" so I install SuperUser to try and replace SuperSU - and delete SuperSU. And Flashify is clinging to the remains of SuperSU. Between my odd model identification (TowelRoot - Status 7 error) and my devices seeming lack of compatibility with.. Anything really (I imagine the two are related). I decide to clean slate it with a factory reset. Which I do from the CWM BIOS (?? Volume up + Home + Power?).
So of course unlike any phone I've ever worked with - a factory reset now means wipe my SIM. (Okay that was laziness and stupidity I should have taken it out first but allow me to grieve). As I should have predicted but didn't it wiped all my backups (foolishly saved onto the internal SD card) and leaves me in the fetal position on the ground making howling noises shedding tears onto the floor.
I can't afford a new phone - or to repair my old one. I need the data off my N4 - who's touchscreen doesn't work - which is problem number 1. And I would really rather not live with touchwiz, or have to do half the process again when I otherwise find the time to get rid of it, so I want to do that now but there are so many errors and I have no idea what I'm dealing with - which is problem number 2.
So please, if anyone can help me out with a)Getting the data off my N4 (it is properly set up as a mass media device) and b)Fixing this seemingly banjaxed S3 and getting pa onto it.
Any help would be really gratefully received. It's been an awful weekend - I also lost a hard drive with all my work and a lot of personal data on it to natural causes.
Thanks - I eagerly await my knight in shining armor.
Have you tried turning it off and back on again?
derekokelly said:
Have you tried turning it off and back on again?
Click to expand...
Click to collapse
I laughed so hard before I broke down crying..
As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.
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.
Before stating my problem I have already serched in other xda Posts but all that I was able to do it to identity my problem and know that my Phone is one of a kind
SO
after trying to install a rom on my device and after failing every time getting error 7 with twrp I tried deleting the device id check in the update-script but after doing that the rom still would not install.
After deleting everything on my phone (yes I deleted the system too) I tried installing the stock firmware from the official website but still no luck and in the update-script in th stock rom was too complicated
SO
i tried installing my rom by sideload but whenever I enter that my device would disapper
I have read different posts watched different videos tried different methods but nothing. The phone is old and if this will not work I will probably throw it from the windows but at this point, since I have been trying for almost 2 weeks, is basically a battle between me and my phone wich it seems I can't win
Thanks!!