Related
I tried searching for a how-to on this but apparently I'm searching inclined.
From what I can gather is it as simple as just dumping the zip onto the root of your SD card and doing:
3. Make sure phone is off then hold Power button and Call Button.
4. The menu opens quickly press the power key over the hboot option.
5. Follow onscreen instructions to install the update. the phone will reboot a few times.
you dont even need to search. go to the development section and then look at the top few, it will have very detailed instructions.
I guess I should have elaborated more and said I don't have my phone rooted and really don't want to go that route. I was just getting confused because everything i was finding on here was people running root but I came across a few things where people said the 2.1OTA Leak was just a straight upgrade, so that is my confusion.
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
but if you have root you can do the downgrade back to 1.5
Android22 said:
but if you have root you can do the downgrade back to 1.5
Click to expand...
Click to collapse
Oh right, I forgot about that, duh It just seems like root would be a better choice.
But to each his own.
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
yeah that is my question, can 2.1OTA just be flashed or does your phone need to be rooted?
I just feel like with root I'll be more likely to kill the phone but I'm going to check into it more again.
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
rheally said:
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
Click to expand...
Click to collapse
yeah I was just reading the thread on going from stock 1.5 to rooted 2.1. Can you give me some of the major benefits of rooting? I'm trying to find really practical stuff, not just the "Well it's cool cause it's like being root in Linux".
And just to clarify you can just flash to 2.1OTA? I'm skeptical of doing that now because I was reading some people think 2.1OTA has a time sensitive date on it.
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Marisa said:
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Click to expand...
Click to collapse
Can you point me to a good nandroid tutorial? tried searching for one but if you know of a good one I'd appreciate it.
I was trying to find a nandroid guide when I did it the first time, but once I discovered that Amon_RA's recovery has it built-in, I decided to wing it and see what happened. It was a lot easier than I expected to be honest.
Reboot your phone into recovery (VOL UP + Power), you should have a short list of options, one of which should be Backup/Restore. Trackball into it and select to make a backup. Let it do it's thing, should take a few minutes. Congratulations, you've made a backup of your phone. You can make as many as you like, they're given names based on the date and time they're created, but you can rename without harm (barring a few characters keep it A-Z a-z 0-9 and you should be good)
Restoring to that backup is as easy as entering the same menu but picking restore instead. You need to have made a backup first in order to restore something.
NOTE: I've written all this by memory, and while it should be fairly accurate, I can't turn my phone off currently to double check that the wording is all correct.
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
I have an application that I write to make going from 1.5 to root a lot easier with a gui application. It will be released very soon for everyone to use. Take a look at my thread for more info. Link is at the top of my signature.
Sent from my Eris using the XDA mobile application powered by Tapatalk
frankspin said:
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
Click to expand...
Click to collapse
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Marisa said:
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Click to expand...
Click to collapse
AWESOME! Thank you I am doing it right now.
NM: got it
Well I got 2.1 on but I did something wrong and can't load rooted 2.1. I get "signature verification failed" message when I load the zip file.
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.
so this is my problem. Im having some issues with my phone and I want it to be changed. The issues really dont matter. In order for my provider to send me another phone they want me to do a master reset. This of course will delete all my apps and settings. As far as I know there is not a backup app that once you restore the phone and apps the restored phone will have all it's app data in place, the icons will be where you want them, etc, just like you would from when you clone or make an image from a Hard Drive from pc... Or is there and application that will do this? My only other option (i believe) is to root the phone to then use an app to do a real backup, then unroot the phone, root the new phone and do the restore. I also have to remove the root from the old phone but can that be done without increasing the counter? This is all a big hassle. I cant believe you can do a real backup/restore on a phone nowadays....
If there is any other way to do it I will appreciate the help. I will have to do this in the next days since my warranty expires in a bit over a month...
Thanks!
You are correct ....
Rooting of the device is needed, then the unroot.
It's the only method I'm aware of in getting a full nandroid backup ..g
Sarge has it right if you want to use backup apps.
If you don't want to root, you will need to flash TWRP or CWR to get the custom recovery and backup. Then make a backup to your external SD card. Use recovery to factory reset. Send the phone away after removing SD card and sim card. The backup is called a nandroid and it is basically an image of the phone.
On new phone flash same recovery then restore the backup. When you start the phone it will be as the broken one was.
You can remove the recovery from the broken phone, but I never heard of anyone getting problems from the warranty people for that.
Thanks both of you guys for the information. I am getting ready to do the root not only for the backup but there are quite a few apps that I want to use that require root that I am going to have to do it.
Now, I started reading tonight and the more I read the more I get confused. Is there an official guide to root the note (specifically AT&T running ICS 4.0.4 if there is a difference) in a way that I can unroot it in the future avoiding tripping any counters?
I have read so many different threads about rooting, they tend to be different so I am looking for the "current" accepted "method" to do this with decent steps if possible. Thanks much!
Whoa whoa, are we forgetting about ADB Backup?
What do you mean CPA?
BTW, I want to root the stock att ics, I am not interested into flashing another rom.
Fernandq said:
What do you mean CPA?
BTW, I want to root the stock att ics, I am not interested into flashing another rom.
Click to expand...
Click to collapse
Yeah I understand, you're wanting to do a full backup of your phone before you turn it in right? Or, at the very least, your apps and settings?
Welp, here you go: no root required.
A quick google search for "ADB backup" should get you the info you need as well.
Also looks like there's an XDA dev who came up with a much easier interface (as opposed to doing everything via command-line, which still isn't that difficult). Might be worth checking:
http://forum.xda-developers.com/showthread.php?p=36499906
Edit: Read your second post, and it looks like you're interested in rooting...I guess I was confused as to your intentions after reading you first post, which just sounded like you didn't want to lose your info after doing a factory reset. Regardless, it is HIGHLY advised before doing any sort of root-related activity to do an ADB backup. That way, if anything goes wrong in the rooting process itself, or if you later decide you want to go back to stock and/or all of your original apps and settings from before the root, you can literally be back with a clean slate within a matter of minutes.
Thanks very much for the link. I have swapped phones already but it will be helpful before I root. THANKS!
after looking at adb I see it would not work for my initial needs as it only can be restored to the same device. I wanted something I could do a backup in the old one and restore that backup in the new one. Anyway, since I am past that anyway I am going to give it a try in theold device.... thanks!
Fernandq said:
after looking at adb I see it would not work for my initial needs as it only can be restored to the same device. I wanted something I could do a backup in the old one and restore that backup in the new one. Anyway, since I am past that anyway I am going to give it a try in theold device.... thanks!
Click to expand...
Click to collapse
The full backup, yes (regarding being able to only restore to the same device) but you could literally extract whatever data you want from the ADB backup using WinRar, then manually push it to your new device.
Apparently ADB backup is broke, it does not respect the -noshared flag and the resulting file is corrupted requiring more processing on the file for it to work... dang it! Seems it has been fixed in JB...
http://code.google.com/p/android/issues/detail?id=28303
http://www.acertabletforum.com/foru...stem-backup-ics-only-root-not-required-2.html
and there is more if you search the net.... Now, why will they not fix it is beyond me. Ok, so the command does not respect -noshared, that is easy to fix, I can just pull my sd card out but making an otherwise broken and unusable file giving the user the false sense of security and not fixing the bug is plain wrong... The only option will be to upgrade to JB but the official upgrade is not out and knowing at&t I wont be for a bit... I am not much into flashing leaked rom although that might change in the near future...
Thanks.
Fernandq said:
Apparently ADB backup is broke, it does not respect the -noshared flag and the resulting file is corrupted requiring more processing on the file for it to work... dang it! Seems it has been fixed in JB...
http://code.google.com/p/android/issues/detail?id=28303
http://www.acertabletforum.com/foru...stem-backup-ics-only-root-not-required-2.html
and there is more if you search the net.... Now, why will they not fix it is beyond me. Ok, so the command does not respect -noshared, that is easy to fix, I can just pull my sd card out but making an otherwise broken and unusable file giving the user the false sense of security and not fixing the bug is plain wrong... The only option will be to upgrade to JB but the official upgrade is not out and knowing at&t I wont be for a bit... I am not much into flashing leaked rom although that might change in the near future...
Thanks.
Click to expand...
Click to collapse
Well crap man, that sucks - sorry! I'm not gonna lie, I didn't read the link you posted as I'm pulling all nighters about 3 times a week during for the busy season of my profession (see my user name lol)...but you're saying that something actually went WRONG with the SDK on ICS firmware - and Google isn't fixing it?? That can't be right...right?
I can personally couch for this method, as I used it to make a full unrooted backup - of stock 4.0.4 ICS - back in October when I rooted my Note for the first time. And the first thing I did (per the rooting tutorial I was following) was verify the backup by doing a restore via ADB before I rooted - and everything worked fine. Like I said, sorry it's not working for you! Have you considered rooting, installing a custom recovery, doing a nandroid backup (and saving it someplace safe of course), then doing a full unroot back to stock + reset your flash counter? There are some great tutorials to walk you through all of that on the Galaxy Note Everything Thread in the General forum, in case that's an option.
CPA Poke said:
Well crap man, that sucks - sorry! I'm not gonna lie, I didn't read the link you posted as I'm pulling all nighters about 3 times a week during for the busy season of my profession (see my user name lol)...but you're saying that something actually went WRONG with the SDK on ICS firmware - and Google isn't fixing it?? That can't be right...right?
I can personally couch for this method, as I used it to make a full unrooted backup - of stock 4.0.4 ICS - back in October when I rooted my Note for the first time. And the first thing I did (per the rooting tutorial I was following) was verify the backup by doing a restore via ADB before I rooted - and everything worked fine. Like I said, sorry it's not working for you! Have you considered rooting, installing a custom recovery, doing a nandroid backup (and saving it someplace safe of course), then doing a full unroot back to stock + reset your flash counter? There are some great tutorials to walk you through all of that on the Galaxy Note Everything Thread in the General forum, in case that's an option.
Click to expand...
Click to collapse
As mentioned in my post....
Root, full backup, and unroot is the fastest method......g
gregsarg said:
As mentioned in my post....
Root, full backup, and unroot is the fastest method......g
Click to expand...
Click to collapse
But what's the point in putting things simply like that when I can write an entire paragraph saying the same thing, but more confusing??
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
AtmaDarkwolf said:
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
Click to expand...
Click to collapse
really this is just an issue I have and nobody else has seen it? Nobody at all has had this problem and knows the fix? Well gee!
Another bump just incase, its happened again: Update yet nothings actually changed, had to 'swipe to fix' root permissions in bootlader menu.
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
AtmaDarkwolf said:
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
Click to expand...
Click to collapse
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
polobunny said:
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
Click to expand...
Click to collapse
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
AtmaDarkwolf said:
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
Click to expand...
Click to collapse
you cant update your phone if it is rooted you have to unroot for that or just temporary unroot the option is available in supersu /superuser
and some apps like root keeper and you have to be on stock recovery
AtmaDarkwolf said:
*snip*
Click to expand...
Click to collapse
Not trolling, the sub categories are there for a reason.
Good luck!
Hello there people!
As you all know every Android user finally goes for the thing called "Rooting" so yes I'm an beginner over it and read alot of discussions but still couldn't find Convincing discussion so I need complete procedure about the Stock ROM and how to back it up in order to Step backward towards it just in case if something strange happens. YES I'll flash a Custom ROM so i'll take the guide as well.
THANKYOU.
Hi there. One thing you will find out about quickly, is that many methods to modify your phone are very specific. Not only to what manufacturer, but what model, what update it is on, if it was purchased from a carrier or unbranded and unlocked, and whether or not there are any warranty issues to consider. Most of the time you can return the device to exactly as your received it and sometimes there is something that is triggered that can not be reset that will show you've modified the phone. So, let us know what you have and we can get you pointed in the right direction to get started.
es0tericcha0s said:
Hi there. One thing you will find out about quickly, is that many methods to modify your phone are very specific. Not only to what manufacturer, but what model, what update it is on, if it was purchased from a carrier or unbranded and unlocked, and whether or not there are any warranty issues to consider. Most of the time you can return the device to exactly as your received it and sometimes there is something that is triggered that can not be reset that will show you've modified the phone. So, let us know what you have and we can get you pointed in the right direction to get started.
Click to expand...
Click to collapse
I have the "Quatro Z4" of the Qmobile company i.e Unbranded but that doesn't mean the unbranded stuff can't get rooted. Yeah I am seeking perfect rooting options and Recovery options with perfect Stock rom Backup.
http://forum.xda-developers.com/showthread.php?t=2542825
This guide has everything you need to root and to use the ClockworkMod recovery which will allow you to make a full backup of your current system (these backups are called Nandroids)
I haven't had a chance to look around to see if there are any roms for it yet, but that guide should be a good head start. I would recommend reading through the thread first to make sure there won't be any surprises.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2542825
This guide has everything you need to root and to use the ClockworkMod recovery which will allow you to make a full backup of your current system (these backups are called Nandroids)
I haven't had a chance to look around to see if there are any roms for it yet, but that guide should be a good head start. I would recommend reading through the thread first to make sure there won't be any surprises.
Click to expand...
Click to collapse
Didn't get you mate? What exactly do I have to do?
I'm not sure what you are having trouble with...? The link I gave you breaks down the steps you need to get started pretty simply...