I was going to post this in reply to this thread, but since I'm new it won't let me: http://forum.xda-developers.com/showthread.php?t=1905674&page=165
So here's my problem. We have 2 Nabi's in our house both rooted with Gapps installed. One is working fine, one was having issues with charging and the screen locking up. I decided to try to un-root the one with the problems and see if I could get a replacement. I then realized that there was a software update, so I decided to try to update first before being without a tablet for any amount of time for a warranty issue.
My plan was to restore to a backup I had, install the OTA update, then re-root it and install Gapps again. All went well with the restore and OTA update, but now I'm stuck at not being able to install root or gapps! I get no errors on the scripts and everything seems to complete fine, but when I boot up again there is no root and no gapps. Post 1647 in the link above indicates it could be a space issue which makes sense, but now my question is how do I delete anything in the system/vendor/app folder without root access?
Both root.zip and gapps.zip were pushed to the tablet and when I select install through TWRP it goes through the process really quick with no errors and says it is complete, but it doesn't appear to be actually doing anything.
Any help/advice is greatly appreciated!
Ok, I think I may have figured this out. I ended up restoring back to my un-rooted stock backup which took me back to version 2.05 with no modifications. I was then able to install root and gapps. I then used the update file provided here to update:
http://forum.xda-developers.com/showpost.php?p=45369304&postcount=1605
When I tried this file the first time before doing any sort of restores it kept failing because I was missing a bunch of files after going delete happy to get rid of all of the bloat. Since I restored to the stock backup it installed fine and I'm now on 2.1 after almost a whole day of messing with this. Now I just have to remove all of the bloat again and restore apps.
So is it safe to say there is an issue with 2.1 and the standard root/gapps files? At least now I know before I try to update the other daughter's tablet. Now to see if the update resolved some of the issues we've been having with this one....
Related
So quite a while ago I rooted using OCLF (also applied the lag fix), and was happy until recently. My phone started going crazy...force closing everything, gallery freezing, maps freezing, battery only lasting 5 hours at the most.
Now 2.2 is out and I really want to update. I'm thinking it would be best to do a complete reset, then update via kies. A friend suggested I just flash 2.2 (friend is a T-Mobile store manager), but will that take care of all my other problems?
Either way I do it, I kinda need step by step directions on how to back up everything, connect to my PC (I've had the phone since July and still haven't connected it), then info on how to flash or update, then get my phone back to the state Where every app worked and my phone would run smoothly.
Please be nice as this is my first post, and thanks in advance for any help you can give (and yes, I've read the Vibrant Bible).
If you're rooted, download Rom Manager (market), open it. Flash cwr (first option), reboot into cwr (2nd option), select reinstall packages (twice if it reboots back to the place you were, the stock recovery).
There, now make a backup.
Reboot, download rom (suggest Trigger 3.2, though 3.3 will likely be uploaded by the time you read this). Move it to /sdcard (internal).
Go back to rom manager and select install rom from sd card.
Suggest you read my guides, signature.
Running 2.3.4 version 4.5.91 ATT/US SBF I believe, stock kernel, unlocked bootloader, rooted, and have Tenfar's CWM recovery.
I accidentally accepted the download for update to v4.5.141 (after hitting "Later" 1000 times), but had wifi turned off at the time and the download never started... now I can't turn back on wifi because the download will automatically start (triangle! with "Enable Wi-Fi to start download update" in notifications), and I don't want to brick the device if it runs and I can't cancel the install.
What can I do to cancel the OTA download and/or install and avoid bricking the device?
Any help is appreciated.
Hmm. I know it's possible to "freeze" the update notification (that is, either use the pro version of titanium backup, or put .bak after the appropriate system app). A few other threads have detailed how to do this.
You just accidentally downloaded it, right? It shouldn't install automatically; it would pop up another "install" vs. "later" prompt once the download finishes. I know there's another post around here (stickied?) that details how to back up your OTA update. You could probably use that thread to find your downloaded file & delete it.
Alternately, since you're unlocked you could always install another rom and skip the OTA process entirely. For example, Nottachtrix is based on the 4.5.141 build and comes with a stock Gingerbread theme if you want.
Thanks, I did see those threads you mentioned.
Before my mistake, I had already tried renaming /system/app/Upgrader.apk to .bak with root explorer, and rebooting to stop the download update popup... it didn't work, and kept prompting me, which I eventually accidentally accepted instead of hitting "Later".
I don't have the Pro version of TiBU Pro; I was thinking of upgrading it to freeze Upgrader when I was trying to stop the download update prompts, but as I mentioned I accepted the download before I could do that.
I was also considering flashing Nottachtrix since that seemed to be the only safe way I saw to update to 4.5.141 with the unlocked bootloader. can I safely flash that now, even though the update is pending?
I'll be honest and say I don't know with certainty. BUT -- I don't see why you couldn't download Nottachtrix on your computer, drop it onto your phone's SD card, and flash it from there (without ever turning your phone's wifi back on). Your phone is booted & not in the middle of an active install. It's just waiting to download a file which would requires your input to begin installing anyway.
If you're really concerned about it, you could do the Seriously Complete Wipe before flashing the new rom by using the following method (thanks CaelanT):
For the best results, when you want to flash a new ROM you should always perform a full wipe in fastboot per the following to make sure you will avoid any unforeseen complications:
reboot to recovery
wipe Dalvik
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
Click to expand...
Click to collapse
One more note: it looks like Tenfar's recovery is considered "old" round these parts, and most roms don't play well unless you flash them using romracer's CWM recovery. So that should probably be your first step. It's here.
thanks for the recommendations. I guess I will uninstall Tenfar's recovery, install romracer's recovery, do the Seriously Complete Wipe, and then flash Nottachrix. Let me know if any of that sounds wrong.
Will I lose my apps or my titanium backup of apps & system data by doing the Seriously Complete Wipe? If so what do I need to do to be able to restore my apps and system data after the wipe & flash?
Hey, no problem at all. (by the way, you don't need to uninstall your current recovery, just flash the new one per the instructions.)
Oh yeah, a second note: you'll need to rename two particular files before flashing the new recovery. From another stickied thread:
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Click to expand...
Click to collapse
Okay, on to apps & data. Yes, you're going to lose all your data in the wipes, but the backups you made will be intact. TiBu is fine for your apps; I use "MyBackup Root" (free on the market) for my contacts, SMS, MMS, etc. After flashing the new rom, you'll have the market pre-installed. Use it to re-download TiBu, restore your backed-up apps (NOT EVER system data. Just apps+their data.), then restore the rest from there.
I did everything, and it worked well. thanks for confirming it was safe and the extra tips!
I had already uninstalled Tenfar's recovery by the time I saw your response. I thought it may conflict, didn't know.
I didn't have to rename those 2 files to be able to boot into CWM recovery... the files weren't present before or after installing CWM recovery and it worked.
Thanks again for the tips on the seriously complete wipe and the MyBackup Root, they worked well.
Almost everything was restored after flashing the ROM except for a few minor settings. I somehow have a ton of contacts because I have all my Google contacts, my Blur contacts (a lot of dupes of Google ones), and a lot of extra old gmail e-mail contacts that I wish it didn't populate. Nothing to complain about because I would rather there be extra unnecessary contacts than missing ones.
The only issues I have is that the ROM shows the 3G img at all times... so I have to do some speed tests and troubleshooting to see if I am stuck in 3G or if it is just the known bug in the ROM where 3G is always displayed.
I have N_01.77.30P radio and I saw some people are running 36 or 37, and some people on AT&T installed an additional APN that improved performance.
If anyone has any input on the 3G, radio, or APN issues, please let me know.
atrix issues
Hello members,
i am new to android and learning to understand the jargon of experts here. Reason for joining xda is following:
I (from India) have a motorola atrix 4g that i purchased from a friend in US (it was on AT&T.)
1) when I start my phone -is says on top unlocked. Does it means it is unlocked / unrooted? and I cannot install the OTA updates from Motorola like ICS 4 coming in Q3?
2) I clicked on system update and downloaded the update over wifi. When it started the install it got failed with a triangle and ! mark. I had to remove the battery and start the phone after which it kept on rebooting . Saw in some forum that i had to do a factory reset and after doing that it worked but I lost everything. I had to reinstall all the apps. Is there a way to reinstall the latest OTA updates from Motorola with doing / playing much with ROM? if not then please let me know a simple and safe way.
3) After doing factory reset i accidentally clicked on system update and now the update is downloaded over wifi but i did not install by selecting "install later" . However the popup keeps coming up and i want to disable it. kindly advise how this notification can be stopped.
Thanks in advance
So, i was happily running the update, when i made a mistake that bricked my phone. I tried to restore a safestrap backup from earlier(still on the leak, though), and it succeeded...but when i tried to reboot, the phone wouldnt boot and the bootanimation was kind of screwy looking, and was blue. Could not get into android. So, i booted up stock recovery to try and reinstall the update, but couldnt because i had replaced the default gmail apk in /system with an inverted one. (The error message specifically referenced gmail.apk) Also, like an idiot, i uninstalled some verizon bloatware via titanium backup. I can , however, still get into safestrap. Anybody have any suggestions?
Thanks in advance for any assistance.
Update: restored to .211 via droidrazr utility, got into stock recovery and reinstalled jb ota. I Iost root, but hey, at least I'm not bricked! Lol....merry christmas to everyone!
Flashed a new rom yesterday. Actually, I just updated it on top of the previous version. Anyway, after flashing this, I 'lost' root. I thought it had somehow actually unrooted my phone after going into settings and turning superuser back on and it didn't work, so I decided just to root again. Went to do that, said it was already rooted, but I went ahead and rerooted. Did not work. ROM Manager and Titanium Backup will not work. However, I can shut the phone off and manually boot into cwm with no problem. I assumed when I flashed another rom, the issue would be taken care of, but today after not getting any signal, I reflashed a rom I had previously used with no problem, but when the phone is on, it acts as if it is not rooted. Any idea how to get my root back? Also, before you say it, I have never been able to restore any backup I've ever made. They all would say md5 mismatch, and I read the solution to this was to delete that file and just make another with the same name. I did that, but now when I try to restore it says error while restoring /system! Obviously, I do not know much about these things so please go easy on me. Thank you in advance for any help and suggestions!
EDIT: Flashed back to cm 10.1 and root seems to be back, but I would still like some insight into why none of my backups will ever restore. I obviously have to be or have done something wrong.
Celeste8157 said:
Flashed a new rom yesterday. Actually, I just updated it on top of the previous version. Anyway, after flashing this, I 'lost' root. I thought it had somehow actually unrooted my phone after going into settings and turning superuser back on and it didn't work, so I decided just to root again. Went to do that, said it was already rooted, but I went ahead and rerooted. Did not work. ROM Manager and Titanium Backup will not work. However, I can shut the phone off and manually boot into cwm with no problem. I assumed when I flashed another rom, the issue would be taken care of, but today after not getting any signal, I reflashed a rom I had previously used with no problem, but when the phone is on, it acts as if it is not rooted. Any idea how to get my root back? Also, before you say it, I have never been able to restore any backup I've ever made. They all would say md5 mismatch, and I read the solution to this was to delete that file and just make another with the same name. I did that, but now when I try to restore it says error while restoring /system! Obviously, I do not know much about these things so please go easy on me. Thank you in advance for any help and suggestions!
EDIT: Flashed back to cm 10.1 and root seems to be back, but I would still like some insight into why none of my backups will ever restore. I obviously have to be or have done something wrong.
Click to expand...
Click to collapse
Couple of things come to mind...
1) Did you open an app called SuperUser and make sure that TiBu was set to "Okay" or "Allow" whichever the option is
2) When you open terminal and type su does the $ change to a # --- if Yes then you are Rooted
EDIT --
Also what ROM did you flash that seemingly caused you to loose ROOT access?
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb