Will I lose root? - Android Q&A, Help & Troubleshooting

Forgive my novice status with both my first Android phone and this site. Galaxy S6 which I rooted using Odin and I believe a kernel it was, from here.
If I run the os upgrade from Smartswitch, what effect will that have one the phone as far as being rooted and all the stuff I've done since being rooted. Thank you very much.

If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.

es0tericcha0s said:
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
Click to expand...
Click to collapse
Thank you sir. Is it simply a matter rerooting the device? Or will every other change I made from root be gone too?

It will wipe your phone, so you will have to redo any mods or settings.

es0tericcha0s said:
It will wipe your phone, so you will have to redo any mods or settings.
Click to expand...
Click to collapse
It wipes the phone every time you do an operating system update? Why would anybody ever do it unless something wasn't working? Unless it's only when rooted? I have good pc skills and some understanding of Linux even, but man I have a lot to learn about these phones.. What about Smart Switch backups? It wipes the phone, how close to before the update will that get somebody? I don't have time to research all this. I may just leave it. This update I'm talking about is a gigabyte btw. That seems pretty huge for a phone.

It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.

es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
It just occurred to me. Firmware IS the Android OS on these phones. That's not the same as a kernel though? With the regular Linux os it isn't. Forgive my ignorance. Like I say this is my first one.

Unfortunalely, firmware is one of those terms that can mean a few different things depending on the situation (like flashing). Firmware in this instance refers to the bootloader and modem files as well for Samsungs. If you don't have the bootloader and modem files (which roms do not install) correctly matched to the OS then you might have issues like not being able to boot or cell service issues.

es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
What I'm wondering is if there's any to have this galaxy s6 just like it is now after many hours of tweaking after one of these updates. I couldn't make heads or tails out of Titanium update.
You are being very helpful sir. Thank you.

Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.

es0tericcha0s said:
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
Click to expand...
Click to collapse
You're making sense. I totally get it. (about starting from scratch) Can I then re-root it with the same UniKernel-v5-920P-072715.tar as before or will I need a new one of those too.? Thanks again.
This is the update SmartSwitch is telling me is available. I don't even know which of this stuff we've been discussing this is. Firmware, ROM or OS update.
Current version: PDA:0H1 / CSC:0H1/ PHONE:0H1 (SPR)
Latest version: PDA:011 / CSC:011 / PHONE:011 (SPR)
Size: 1612 MB

That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.

es0tericcha0s said:
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
Click to expand...
Click to collapse
Whatsa TWRP + SuperSU zip Is that a tool and file for getting this update?
Sorry man. I've had this phone for less than 2 months and it's my very first one.
I do appreciate your patience. I've been a PC support guy for 16 years. I know what it's like.

TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy. ☺

es0tericcha0s said:
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy.
Click to expand...
Click to collapse
I have SuperSU already.
These are some truly terrible directions unless you already know enough to not need them.
https://twrp.me/devices/samsunggalaxys6sprint.html
Will installing TWRP effect the root method I've already used?
Will installing recovery effect any of the multitude of configurations I've already done?
Does this then allow manual installs of OTA updates without losing root or any of your configuration customizations?
Is it JUST the recovery partition were dealing which stands alone from the os?
Does Nandroid backup then encompass the recovery and os and rom etc? Meaning are they all backed up and custom recovery via TWRP was what made that possible? Or do you have to make your current config the recovery itself in order to do a ghost style backup and restore if you jack yourself up later? OR is not even this a ghost style restore?
Maybe it's just me, but the terminology is very confusing and I can't make heads or tails of what I'm even talking about with all this.

Tried to make backup with TWRP...
I guess whatever I flashed it with last time won't let it boot into recovery or the bootloader or whatever it's called. If I tell TWRP manager to reboot and do backup it just goes to the menu for rebooting and wiping cache etc. If I specifically go to "reboot to bootloader" it just reboots into android. I went to install a custom recovery and it said that if the location for the recovery is wrong it could brick the phone. I have no idea if it's right or wrong or if the root method I've already used is effecting this or not.

Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.

es0tericcha0s said:
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
Click to expand...
Click to collapse
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?

About this....
You were saying up HERE that if I run this update with smart switch I would lose root, but if I use TWRP to do it, I won't? Is that right? Thanks again.

Tiribulus said:
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
Click to expand...
Click to collapse
This should mean that the recovery is installed. You can verify by using the app to boot to recovery or via powering the phone on by holding the Power, Volume Up, and Home buttons together as you restart. You should notice a recovery booting message in the top left and then you can let go of the buttons. Once there, you should perform a backup of the boot, system, and data partitions. If you have an EFS option, I would back that up too for safe keeping. It's rare that it would get corrupted, but best to have a backup just in cause.
If you update via Smart Switch, you will definitely lose root, as well as TWRP. Most likely, a developer has posted a rooted version of the update that you can use TWRP to install.
So I was looking into this a little closer for you and realized that the preferred method of updating and rooting the update you are trying to get involves using Odin to install the full update package, then reflashing TWRP, and using a newer version of the kernel to root. However, from some of the user comments about it, it seems like it might be better to wait till Samsung has released the source code of the kernel for the OI1 update. The kernels based on the slightly older 5.1.1 builds will work, but some people were experiencing random issues such as reboots or other oddities. I don't think OI1 has anything in it that would be worth losing root over or possibly having things run oddly. The alternative would be to update via a rom like this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417

Related

[Q] Cancel OTA update to avoid brick

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

Moving files to a phone stuck on bootanimation

Recently my phone has bricked, every time I connect it to a power supply unit, it boots, but the boot process stop right before the actual loading of the UI (stuck on the second part of bootanimation). Well, I think I could fix this by restoring the stock /system/fonts/ folder content (because I alterated it right before bricking). So, how could I push those files into the phone without being able to load the UI?
Stock S3 ROM JB 4.3 build MK6. Stock recovery. Can get to recovery and download mode. Tried with adb, but there's no way (installed drivers, java SE, kies, Android SDK, Google drivers, uninstalled all, reinstalled all, uninstalled kies and so on..). I would prefer not to lose my data, because I don't have a recent backup. Actually I thought to install a custom recovery and hence move the files I want to the location I want, but installing a custom recovery could make me lose my data.
Thank you.
Fanaticism said:
Recently my phone has bricked, every time I connect it to a power supply unit, it boots, but the boot process stop right before the actual loading of the UI (stuck on the second part of bootanimation). Well, I think I could fix this by restoring the stock /system/fonts/ folder content (because I alterated it right before bricking). So, how could I push those files into the phone without being able to load the UI?
Stock S3 ROM JB 4.3 build MK6. Stock recovery. Can get to recovery and download mode. Tried with adb, but there's no way (installed drivers, java SE, kies, Android SDK, Google drivers, uninstalled all, reinstalled all, uninstalled kies and so on..). I would prefer not to lose my data, because I don't have a recent backup. Actually I thought to install a custom recovery and hence move the files I want to the location I want, but installing a custom recovery could make me lose my data.
Thank you.
Click to expand...
Click to collapse
I have been flashing roms for years and never lost any data by flashing a recovery just make sure you read the guides and you will be ok.Make sure if you do flash a recovery to backup your data before attempting anything else..But remember to backup just your data not the rom because you will be backing up a faulty rom (because you altered/deleted the system fonts)
tallman43 said:
I have been flashing roms for years and never lost any data by flashing a recovery just make sure you read the guides and you will be ok.Make sure if you do flash a recovery to backup your data before attempting anything else..But remember to backup just your data not the rom because you will be backing up a faulty rom (because you altered/deleted the system fonts)
Click to expand...
Click to collapse
I don't see the point of your answer. Anyway thank you.
Fanaticism said:
I don't see the point of your answer. Anyway thank you.
Click to expand...
Click to collapse
My point is your are in a bootloop because you messed with system files! I was stating that your chances of losing data because of flashing a custom recovery are low and by doing so you can back up your data in recovery and get yourself out of a bootloop.
I suggest you do a lot more reading or you will mess up your phone even more this is a easy fix if you read the stickies and tutorials..
tallman43 said:
My point is your are in a bootloop because you messed with system files! I was stating that your chances of losing data because of flashing a custom recovery are low and by doing so you can back up your data in recovery and get yourself out of a bootloop.
I suggest you do a lot more reading or you will mess up your phone even more this is a easy fix if you read the stickies and tutorials..
Click to expand...
Click to collapse
Oh ok, now I got what you intended. However I really didn't any massive modifying to the file system, I just wanted to change the fonts, I didn't think I would have needed a guide to follow and warnings about that.

Phone won't boot; need to restore a deleted system file

Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options. It is also relevant to know just how much information you want to recover.
File replacement:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- will retain all existing data & customization. Maybe worth a try, but I don't recommend it
Dirty-flash:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You will be able to flash a (custom) samsung-based firmware, which WILL overwrite /system, but will NOT overwrite your /data partition, likely allowing you to boot and properly back-up the stuff you want to keep, or even create a nandroid of the existing setup. <-- Will retain all existing data, will lose /system customisations. I have used this method.
Start-fresh:
Use desktop-Odin to flash the official firmware may be your only other option, which will retain everything in internal memory (photos, downloads, music, nandroid backups), but not messages, or any app data.
-Cyril
Mr. Barker said:
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
Click to expand...
Click to collapse
cyril279 said:
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options.
Click to expand...
Click to collapse
Well I do have CWM installed, but am curiously (and annoyingly) unable to boot to it now, for whatever reason. It boots to stock recovery instead, every time.
cyril279 said:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- maybe worth a try, but I don't recommend it
Click to expand...
Click to collapse
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Mr. Barker said:
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Click to expand...
Click to collapse
I would be glad to provide more detailed information, but I prefer to do so from a desktop computer, and I won't be near one for several days, so this may be a slow process unless one of our peers steps in to help.
In the meantime, you should gather:
-Odin 1.85 or 3.07
-A Siyah s2-v5.x or s2-v6.x .tar.md5 kernel (for the i777 or i9100)
The latter you can find at http://www.gokhanmoral.com
I will outline the process in a later post, explaining the purpose of each step.
Sure, I'm OK waiting a few days. I appreciate the help, I haven't done any flashing in quite some time and don't want to make a mistake, especially with all the important data that's at stake.
Thanks.
File Replacement Method
1) Use desktop Odin to flash Siyah kernel
-Installs a kernel that will allow you to perform a nandroid backup, and MAY allow you to adb push the missing file to the device.
-This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
-If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Adb push missing file to /data/path_file_belongs
5) Shell chmod XXX the missing file
-to correct file permissions; that 0.xml file has -rw------ on my device, which translates to 600 (I think)
6) Flash appropriate ajk kernel
-for stock jb, use "NoSwap" http://forum.xda-developers.com/showthread.php?t=2110542
-custom kernel that will boot stock rooted android.
7) Attempt Reboot into android
-If successful, reboot to recovery and perform another backup.
-If not successful, then we use a different method.
This is the trickier method of the three, but will retain all customization if it works. I have not tried it, and we're assuming that the missing file is actually the problem.
Please be sure that you are comfortable with all of the steps before attempting any of them. I will be able to provide step by step instructions, but not for several days.
Happy flashing,
-Cyril
Well, that was fun. Followed the instructions to a "t" and even learned some things. But, sadly, did not achieve the results I'd hoped for.
I was indeed able to push the wallpaper file over to data\system\users\0 and CHMOD it. But after flashing AJK "NoSwap" the phone shows the "Android is upgrading..." message, with "Starting apps." trying to process. But it doesn't. The little circle swirls a bit, then the screen goes black. The "Starting apps." message appears again, then the screen goes black again. And then it repeats this cycle forever. I eventually got irritated and yanked the battery.
So... *sigh*... what's my next best option?
The Nandroid backup completed successfully? If so, that's great, any APP customization is likely captured in the backup. How well they will restore is a different concern, but we need to get the device booted completely into android first.
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
cyril279 said:
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
Click to expand...
Click to collapse
I say wipe caches and fix permissions first. If that doesn't work format /system, and install a ROM of the same version of android.
After that if it's still not booting suck it up do a full wipe and start from scratch.
Sent from my SGH-S959G
@Mr. Barker
If the cache wipes / permissions fix doesn't help, then our next attempt is:
**this assumes that you were running stock Android 4.1.2 when the trouble began**
get i777UCMD8 cooked v2.2 onto a flashdrive, (or prepare it for sideload)
reboot to recovery
format /system
install cooked v2.2
attempt to boot into android
OK, I'll give it a try, thanks.
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM is needlessly flashy.
Mr. Barker said:
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the black notification pull-down menu? This ROM sets it transparent by default, which doesn't work for me.
Click to expand...
Click to collapse
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
To change the notification background go to the mods section of the installer, and just install the black notification background.
Sent from my SGH-S959G
mr-cook said:
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
Click to expand...
Click to collapse
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
"needlessly flashy"
Simply asking 'how to change the icon' is sufficient, and inherently implies that you prefer something different.
Cooked v2.2 is definitely quicker than stock;
The premise of both cooked and shostock are that they have taken the stock firmware, and stripped it down of unnecessary junk, and run it over a well-optimized kernel for the best touchwiz experience that you could possibly have on this device.
If your firmware desires are different than what cooked v2.2 provides, then I suggest creating a nandroid backup, wiping /system, and giving shostock a try. It's the other touchwiz favorite for the i777, packaged with a different very good kernel, and also runs quicker than stock.
Mr. Barker said:
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
Click to expand...
Click to collapse
To close the loop, now your initial boot screen is a yellow triangle with an exclamation point? It doesn't affect the functionality of the firmware at all, but if you prefer to have the correct initial boot animation, then you'll need to follow an additional procedure.
Summary:
Nandroid-backup desired setup
Flash official stock-firmware to the device via Desktop-Odin (clears the warning)
Root & recovery via Framaroot/Mobile-Odin (a method that does NOT trip the custom-flash monitor)
Restore nandroid to return to the established custom setup
Procedure:
gather onto internal memory, or micro-sd:
-Framaroot
-Mobile Odin APK
-Mobile Odin flash kernel for i777
-Boot.img (extracted from your chosen firmware.zip)
boot to recovery
perform nandroid backup
^^ this MUST complete successfully
perform factory reset
boot to download mode
flash official UCMD8 using Desktop ODIN
^^ clears the custom-flash warning
install and use framaroot
^^ uses an exploit to establish and manage root access
install mobile Odin and the mobile Odin flash-kernel
^^ the method that will NOT trip the custom-flash monitor
flash the boot.img via Mobile Odin
^^ flashes the kernel and recovery of the firmware that you are going to restore
boot to recovery
restore nandroid backup
enjoy
-Cyril
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup? Or could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards) My point is, are nandroid backups firmware-specific?
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Before all this I've never flashed anything but stock firmware, and never had to create nor restore nandroid backups. So most of this is all new to me. But I enjoy the learning process.
Mr. Barker said:
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup?
Click to expand...
Click to collapse
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Edit: As Mentioned below, a CWM nandroid will restore the entire backed-up firmware installation, which can be done over ANY firmware.
If the goal is to keep your App data across different firmwares, then a Titanium backup restoration may be what you're after. /Edit
Mr. Barker said:
[...]could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards)[...]
Click to expand...
Click to collapse
I don't think that the stock recovery allows to restore nandroid backups at all. The restrictive nature of the stock recovery is one of the more practical reasons to root the device & use a custom kernel.
Mr. Barker said:
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Click to expand...
Click to collapse
Mobile Odin will flash a zImage, no need to rename it. I didn't check to see that shostock or cooked use a zImage instead of boot.img.
cyril279 said:
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Click to expand...
Click to collapse
?? I thought that because a nandroid copied (backup) and then formatted/recopied the 5 partitions (restore), that it didn't matter what firmware you had installed?

Factory Reset phone- trouble accessing storage

I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
KStef56 said:
I'm new to rooting and it took me a while to get it working on my phone. It was going great though for over a year until today. I updated my phone with an AT&t update and after it booted me to the recovery area which I believe is called teamwin. I updated that too (like I have a couple of times) and my phone completely stopped working.
Click to expand...
Click to collapse
You need stock recovery, as well as stock ROM (never rooted, unrooting does not work) in order to update OTA.
The phone tried to boot into stock recovery to install OTA; and since you don't have it (TWRP is a custom recovery), update fails.
General rule on Android, is that OTA updates don't play well with root. You should always research (for the specific device) before applying an OTA to a rooted device. That includes requirements to OTA, and also the expected results. On past devices, I've seen it not uncommon that an update removes the ability to unlock the bootloader and root. So its good to know what you are getting into before installing OTA.
KStef56 said:
After troubleshooting for a few hours I was able to boot into safe mode, which I then did a factory reset. I've been able to install apps, but I none of them seem to work. Spotify is giving me error messages saying, (no storage area found) and when I installed zedge to look at ringtones and whatnot I couldn't install anything through there.
I'm assuming I have to redo the root process, but I was hoping there was another fix I'm not seeing. Like I said I'm very new to all of this. Any help would be awesome and also if I have to reroot is there any specific I have to do? Like getting rid of what I've done already?
Click to expand...
Click to collapse
I suspect that your internal storage got corrupted somewhere along the way (as you were trying to OTA, recover, etc.). I'm not clear on the current status, you are still on the stock rooted LP ROM, with TWRP custom recovery?
If you still have working TWRP, I'd suggest booting into TWRP, select Wipe from the main menu, then the option to "Format Data" which will format internal storage. Strongly suggest not picking any other options (particularly in "Advanced Wipe" section) unless you know exactly what you are going. Lots of posts on here, by folks that delete things like System (OS) and wonder why there is no longer any OS!
After formatting internal storage, reboot and see if you still have the same issues accessing storage. If so, you may need to RUU back to full stock image, and root again. But we'll cross that bridge if the TWRP format storage option doesn't work.

OnePlus X soft-bricked after version update

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

Categories

Resources