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.
Related
EDIT: 12/23/2012 3:19AM.. Doing a little research I figured out what the issue was. Used Brian Gove's Guide
[How To] Reset your phone in order to return to Verizon(Updated 12/11/2012)
From Step 5 Onwords and everything works great.
.. I am still stumped on exactly what happen. I am almost positive it was because of the new file structure..
Just Proves that with a little patience and smarts anyone can use the resourced and tools here to solve their own android problems without bothering anyone haha.
Thank you all for your articles and Merry Xmas / Happy Holidays to Everyone!!
now.. I gotta unlock my boot loader and start all over..
Soft Brick.....
I was looking around and I cant seem to find a post that really solves my problem.
I have a Verizon S3 that I rooted and flashed to CyanogenMod Nightly build and everything was working great.
I used Rom Manager Premium and it updated me to update to CMW 6023. I went ahead and updated.
I saw that there was an update for my Daily As well 12/22/12 so I went ahead and used Rom Manager to download it and install it for me like It did with my last 16 Roms. That Rom had some strange things going on so I flashed to an older rom 12/20/12 and that rom was buggy as well.
Finally I decided that I should just stop with the Daily's and use the stable. When I loaded the Stable things started to still act strange. Mostly the Keyboard would not work and keep crashing. I decided then to just reload my original backup from Verizon.
Before I went in to recovery i took a look at my files and backed everything up. However then I noticed something that was not there before, a folder /0 with most of my main files inside.
I went into CWM v6.0.2.3. and tried to do a restore to my original nandroid backup from verizon but it looks like it failed.
It Says "Error While Restoring System" and kicked me back to CWM
Now when I reboot all I see is the White "Samsung Galaxy s3"
Did I Screw the pooch on this? Kinda nervous haha.
I am Posiive its a Soft Brik and hoping there is a way to fix it.
I can however get to Download mode. If anyone knows a great guide to help me reflash with Odin that would be fantastic.
thanks guys, been a long time reader and this is the first problem I have really had.
I apologize if this has already been over in a post.
Just a quick step breakdown would be great. I am really hoping that I didnt brick my phone.
Thanks for the help and Merry Christmas / Happy Holidays to everyone.
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.
I've been running Jans ported GPE rom on my work I9505.
I chose it as it is so close to stock I could remove root after install to use company email.
However it could be a little more stable. RR's and FC's are taking their toll.
I tried using ART and that bricked the phone so I reinstalled fresh.
Just now I thought I was going through another RR when I was in a hurry to open a page in Chrome and it will no longer boot, just the coloured circles over and over.
Can someone recommend another Rom that's very stock KK that would be ok to run with the phone not rooted?
I am guessing that the more custom Roms would need root access due to the higher functions they support.
Thanks
Vic
These are the forums for the SGH-T959V, a phone that had its last OEM ROM from Gingerbread. You probably want a different section of XDA.
---
Posted from whatever phone booted today
Ha ha, you're right. I read it as Galaxy S4 4G. I will try again.
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..
Alright, so before I say anything, I have not visited this site nor have I conducted any business with roms, TWRP, etc in the past year let's say. I used to be an avid visitor, flashing a bunch of roms, but was tired of the amounts of bugs and problems that I found. So I restored my back to stock on my G2 from TWRP. Been using it for about 1 year now, just so I didn't have to deal with problems... until now.
So a few days ago I saw an update in my notifications, but for the love of God I cannot remember what it said. All I know was that it needed to update something about the phone, not for example an app. Today I decided just to update it, and suddenly the phone rebooted into TWRP. I thought that was weird so I rebooted it again, and back into TWRP I was. I tried restoring some old backups to see if they would maybe boot into it, but once again it keeps bringing me to TWRP. Now I am stuck in a position where I am unable to use my phone and am not sure what to do next. I haven't visited these forums in a while either so Im not sure where to post this xD.
Honestly if someone can suggest something or help me in any way, it is appreciated. If there is anything I can do to help, just say the word.
I am using the Canadian Variant of the LG G2, from wind. I believe it is a D801 but not an actual D801, as I remember being told to only flash D803 roms as it was basically a D803. Not sure if that helps. Im planning on getting a new phone so I just need this one to hang on a little bit longer.
Thread closed / Duplicate