Related
You've probably heard about the Carrier IQ fuster cluck by now and, if you're like me, are up in arms and want it gone if you have it on your phone. I would suggest that you don't use the removal tool yet...
I am rooted using the "stock" method here: http://forum.xda-developers.com/showthread.php?t=1342728 and just downloaded the tool from http://forum.xda-developers.com/showpost.php?p=17612559&postcount=110 to check for CIQ on my phone (it was there) and purchased the license to remove it, which I also did. I then rebooted the phone as instructed but can't get past the SGS2 splash screen.
Can someone please help me... if I have to flash a new rom, fine - I can accept that. I should have been thinking before I did anything but I had only rooted up to this point and didn't have any Nandroid backups or anything and that's my fault. However, I used the internal phone storage or SD as my primary file location and need to access it to grab my files. Is there any way to do this if my phone isn't booting up?
I read another thread (can't seem to find it now I was on my mobile device), where another person did the same exact thing as you and had to ODIN to stock and start from scratch. The phone isn't bricked, but it's not going to boot now.
I'm disappointed because according to Caulkin's ROM CIQ is removed, but I used the tool you are speaking about as well and it states that CIQ still exists. I was going to pay the .99 and have it removed since that tool supposedly works for Samsung devices, but after reading that other thread and now yours - I'll pass.
I'd recommend re-ODIN'ing your phone, not from experience with the issue but just from what I read from the other thread - you aren't going to have much of another option.
EDIT: Here's the link to the thread with your exact questions pretty much and the answers you can expect - http://forum.xda-developers.com/showthread.php?t=1360988
Ugh. Thanks for the reply... this is so annoying. If I go that route, it's going to wipe all of my internal SD memory, too? I've already lost access to the items on my external card because I had that encrypted... but I used my internal for primary storage and have a LOT of items on there of great importance...
Starting from scratch I can deal with - losing all my files I can't.
What package are you on? It works on EG30, but not on EK02. Framework is different.
Worked find on my EG30. Waiting for it to be updated to the EK02 package. Should be around soon.
Not trying to nitpick, but you should always have at least two backups of your internal and external memory. That's at least what I do, usually I backup all my files once a week and do a NANDroid once a week. Saves the headaches from ever happening.
You could try three-fingering to see if you can get into recovery and see what you can do from there, but I don't think you are really going to be able to do much. This method has been tried and proven to soft-brick your phone.
I was going to attempt this method this morning and then did a simple search on XDA and found it had soft-bricked that guys phone I linked you too. That's all it would have taken...
Good luck.
I have some backups, as well as Titanium Media Sync running and Google+ uploading photos, but there are always gaps. Unfortunately I haven't done a 'hard' full drag and drop back up for a couple of weeks, and you can generate a lot of data in that time.
To tell you the truth I'm a little unsure about how or what it takes to have the ability to do a Nandroid backup. I've done plenty of them in the past but what I mean is that since I just did the stock root method I don't know if I needed to install CWM or something like that to get the ability to do a Nandroid. I just haven't had the time to research that fully so I hadn't done one yet.
For what it's worth, the ****storm about the CIQ thing just really exploded in the last 24 hours or less so I didn't think there was anything to look up about the removal tool. I guess I was so distracted about the BS that is Carrier IQ and just wanted it gone, so I ran the tool without thinking there was a database of information on it already. It was my bad.
In the automated rooting thread, you could choose Option C and select a kernel+CWM to install EG30+CWM and EG31+CWM are provided.
update: Fixed. Whew. Thanks for the suggestions, especially, sfhub. Did as you said over in the other thread http://forum.xda-developers.com/showthread.php?t=1342728&page=26 ... will post followups there but basically flashed the stock rom in odin and phone booted back up like nothing ever happened. Well, the only difference really was the media scanner took a considerable time longer than usual on that first clean boot. Thank you so much, again, and see you over in the other thread w/ a few more questions...
dbaybay said:
I read another thread (can't seem to find it now I was on my mobile device), where another person did the same exact thing as you and had to ODIN to stock and start from scratch. The phone isn't bricked, but it's not going to boot now.
Click to expand...
Click to collapse
Unfortunately, that was probably me. I freaked out too but just Odin the stock tar and all is well.....other than now being on E31 and now can't get any ek02 goodness.
Sent from my SGSIIE4GTuvwxyz....should I touch my nose or walk a straight line now?
When last Feb. I finally switched from my iToy to my N7100, I thought that 'flashing' was something that some perv did while wearing a raincoat.
(Hey, I'm pushing 70)
I Finally got my device rooted. I know that it's rooted because while using CF Auto, It wanted me to flash a Triangle Away update, and my binary count went down from 22 to one... so I know at least that worked.
Overjoyed that in Odin, when flashing I first got the notice "Reset!" and then after a few minutes and a restart, I got the "Done" notice (or whatever it said) as I never unplugged from the USB as it says you're supposed to. I just forgot.
Prior to "upgrading" to 4.3 Indian version, I had the stock Rom 4.1.2 running the Perseus Kernel... loved it, but upgrading to 4.3 has turned out to be the worst decision so far.
I still have a lot of Root apps on the phone but they don't work, but as I said, Triangle Away did work.
Should I uninstall the existing ones like Tit. Backup Pro and a few others and re-download them?
Does CF Auto Root automatically install SuperSU? Or should I uninstall that and re-download that too?
One last question....
Assuming that I do have Root, and I'm able to get Titanium Backup Pro working and am able to freeze and/or uninstall the Knox files... What about the ODEX files with Knox.
On this site, I have heard both pieces of advice... Delete and not delete the ODEX'd files.
What is it?
Nobody ever comes up with a definitive answer on this site... it's just a bunch of opinions, usually with the disclaimer, "Worked for me", or something like that... combined with the fact that I really hate working with the Windows partition on my Mac to do the flashing.
Oh, one more thing.
I'd like to go back to the Perseus kernel which somebody mentioned here on XDA.
Are there any kernels for the N7100 that are only useable with 4.1.2 that I should NOT use with 4.3, or does it matter. In other words, would it work with 4.3 as it did with 4.1.2?
Too bad that I don't have somebody like ChainFire living next door. Haha!
I have to thank the XDA site for most of my knowledge since last Feb. when I thought that rooting had something to do with digging up a tree in my front yard.
One more thing (again), I just got an update for Rom Manager Premium and it looks like I can download a CM stable release, which I'm gonna do as soon as I get some of these things ^^^Above answered and ironed out.
I'd like to stick with AOSP as opposed to AOKP but I'll do anything to get away from this current ROM.
Thanks in Advance to anyone who can answer some of these Noob questions.
1-ok i think that you have a custom recovery now, i had these issues a lot on 4.3, if you have custom recovery TWR or CWM you can install any rooted 4.3 rom, but before you do so make sure you backed up your efs folder (VIP you will lose signal if this folder corrubted), after a clean install of any rooted rom, just install ur apps again, if you don't have custom recovery you will need to flash any recovery from Odin, if you can't install recovery from odin so this will be bec. of knox, report back bec. this is another story.
2- some kernels works fine with 4.1.2 or 4.3, and some old ones are only 4.1.2, so make sure that you will flash the right kernel (e.g. devil, AgniPure Stock, ....)
3- don't try to update to CM now, frist make sure that you have a fully working rooted rom with custom recovery install, i also don't recommend flashing roms using any app (rom manager fore example), i think the best flash is the one you do from recovery with clean flash
Just A Follow-Up...
Hey, thanks, evaworld!!!
UPDATE:
I decided to try Root Explorer again (It never worked before to delete anything before this time) and do a search for anything with Knox in it.
I found everything Knox and checked all the boxes except for the ODEX'd files, hit the trash can and wow... it asked for Root privileges. I gave it, and everything was gone in a flash (Pun intended).
Then I tapped on Ti Backup Pro and got the dreaded 'Android device I.D. changed' message so I came back here to XDA and read literally every post on it (Again, opinions are divided) and decided to ignore.
After that, nothing was working for me in Google Play, so I just deleted the data in Google Play Services, Google Play Store, and now I'm waiting for it to take effect in Google Play... whenever I did that in the past, it usually took a couple of hours for it to register. (?)
Now, all of my Rooted apps that I've tried so far are working, but somewhere along the line they pushed Samsung Link on my phone even though I've had Samsung Apps disabled since day one.
The funny thing is that with a Binary Count of 22, I did absolutely nothing differently than this time (Except for an abortive try with Philz_Touch that I don't particularly like the GUI in P_T)... same USB cable, same port, same Windows partition on my Mac, etc. etc. it took this time and I'm pretty overjoyed!
I'll follow evaworld's advice on the ROM... better not throw too much into the mix until I decide that everything is all ironed out.
And, yes, I did click the "Thanks" button for you.
Very good that you have root, but also note that your setup isn't so stable (besides the fact that 4.3 isn't very stable with root apps e.g. I always have problems with titanium and Super and alot of other apps that requires root) , so just clean install a good 4.3 app (I recommend DN3), and after that you are free to do whatever you want (don't forget efs backup in sage place).
Sent from my GT-N7100 using XDA Premium 4 mobile app
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
happy4ya said:
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
Click to expand...
Click to collapse
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Aerowinder said:
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Click to expand...
Click to collapse
Thanks for all the info. So I definitely have the FLO model.
I would like to use Titanium Backup for Root and a few other things that need root access so I definitely want to do this.
Also, being that this tablet has no micro SD, I definitely want to have read-write access with a USB drive. I've had this for almost a week already and I haven't loaded anything into it yet because I figured I'd be wiping it. I really don't want to mess with stock because of the lack of a few things. I really just can't stand having devices with restricted use. That's not what I paid for.
I never used Kit Kat before and not sure if I'll like it. Do you know if you can go back to 4.3? I know with some of the other devices (like my Galaxy S3 phone), once you update it OTA, they lock stuff up and you cannot roll back.
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
happy4ya said:
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
Click to expand...
Click to collapse
You can roll back to 4.3. Google hasn't gone full Apple yet. But I strongly advise against doing so, as it's a large step backwards.
Understood on stock OS, agree no options anywhere. Slimkat+franco.kernel+banks gapps. You won't look back. Also in developer options, switch to ART. Dalvik sucks. If you're using Banks' minimal gapps, the lack of some syncing libs (for the AOSP calendar nobody uses) will cause random FCs until you reboot a second time. Nothing to worry about. Just grab the Google Calendar, or whatever calendar you use, from the play store and freeze the AOSP one with TiBu. Another FC you might see is gms.location. It should only happen once. Something with play services.
Once you are rooted, you can grab BetterBatteryStats to see what's killing your battery. On stock installs, it's mostly going to be location-based stuff keeping it awake. You already turned off reporting, but you also need to switch location mode to Device only.
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I also have a similar issue as the OP. I am currently rooted, stock rom. ZVD update has downloaded and is ready to install. However, what would be the nessesary steps to take prior to updating my phone? I dont care if I have to re-root again. I rooted me device using IOroot25. How can I unroot?
Thanks!
Supersu has the option to unroot permanently. Doing a full unroot. Weather the system accepts that, I'm not sure.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
...Only safe way right now is to tot back to stock zvc...
Click to expand...
Click to collapse
But, reflashing the ZVC tot will erase all data, correct?
jlv3 said:
But, reflashing the ZVC tot will erase all data, correct?
Click to expand...
Click to collapse
Yes, complete everything. Data, pictures, documents, downloads.
Sent from my Nexus 7 using Tapatalk
mtcellph said:
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
Click to expand...
Click to collapse
From what i understand , you will need a stock ZVC recovery and boot loader to apply the update. if you have any modification done in ROM (debloat/deleting/modifying system files) then the update might not complete.
So flash stock aboot(bootloader), recovery and kernel and then only apply the update.
TOT reflash is too cumbersome process and requires lot of restoration of apps setting etc.
I have same situation and am searching for stock files from ZVC. Please if any one has these stock file please do share.
Cheers
Phuq! I wish I read these forums more frequently.
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if there is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
ZVD bit me too-not sure how, NEVER told it to install
adamant_orcinus said:
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if te youhere is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
Click to expand...
Click to collapse
Sorry Dude, I was in the same spot, maybe I can save you hours of reading. This is what I had to do:
http://forum.xda-developers.com/showthread.php?t=2432476 it's the dreaded tot to zvc
Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!
Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!
Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?
Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app
Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.